Bug#986655: Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable
Package: lighttpd Version: 1.4.57-1 Severity: grave Justification: non serious data loss whe made force reload the log fiel are not more used.. this again happens only with the shitstemd case, cos sysvinit script are in the fly converted to, so the it display a "Warining" about log output is incomplete.. in some cases causes spurious socket break serveruno:/etc/lighttpd/conf-available# service lighttpd status ● lighttpd.service - Lighttpd Daemon Loaded: loaded (/lib/systemd/system/lighttpd.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2021-04-08 09:00:10 -04; 8h ago Process: 3997 ExecReload=/bin/kill -USR1 $MAINPID (code=exited, status=0/SUCCESS) Main PID: 8936 (lighttpd) Tasks: 1 (limit: 4915) CGroup: /system.slice/lighttpd.service └─8936 /usr/sbin/lighttpd -D -f /etc/lighttpd/lighttpd.conf abr 08 17:24:22 serveruno systemd[1]: Reloading Lighttpd Daemon. abr 08 17:24:22 serveruno systemd[1]: Reloaded Lighttpd Daemon. abr 08 17:25:24 serveruno systemd[1]: Reloading Lighttpd Daemon. abr 08 17:25:24 serveruno systemd[1]: Reloaded Lighttpd Daemon. *Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable*. serveruno:/etc/lighttpd/conf-available# service lighttpd restart Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#986603: courier-MLM : it runs as root ? or we must manually set up as coureir user?
Package: courier-mlm
Version: 1.0.14-1
Severity: grave
Justification: renders package unusable
now found is a debian problem, the courier-mlm documents said in clear way
that cannot be use any shell constructs or script trick, and cannot use quotes,
the debian file has: PIDFILE={PORT}.pid and with previous PORT as
PORT="/run/courier/webmlmd" and init sysv scripts uses quotest..
so i always got this error wherever tyope of init system i used
abr 07 12:56:37 isomaker systemd[1]: courier-mlm.service: PID file
/run/courier/webmlmd.pid no such file or directory
after disabled all the systemd and start in sysvinit only mode
I got the same error.. i check that in debian package the courier-mlm
defines PIDDIR as a shell banish.. and use coutes in the sysvinit script,
so both units will fail always
i try to restart the courier mlm after correctly setup the lists,
the PIDFILE (with no quotes or shell constructs) and PIDFILE,
usin hardcoded path and problem solved..
so the solution is remove the shistemd unit (due the unable to handle
the problem of the mail list empty, check bug #979161 [1] )
or fix the pid definition with hardcoded path in the webmlmrc file
courier sources defines @piddir@ etc etc and when install uses hardcoded paths
so must fix that!
1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979161
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
El mié, 7 de abr. de 2021 a la(s) 13:03, PICCORO McKAY Lenz
(mckaygerh...@gmail.com) escribió:
>
> i try to restart the courier mlm after correctly setup the lists
>
> but i got this using sysvinit or shitstemd :
>
> abr 07 12:56:37 serveruno systemd[1]: courier-mlm.service: PID file
> /run/courier/webmlmd.pid no such file or directory
>
> after check the file is there, but owned by root and named differently:
>
> /run/courier/webmlm.sock
> /run/courier/webmlm.pid
>
> the shitstemd service unit defined with the stupid "d" at the end.. i ask
> them:
>
> where is defined and what is the defaults for courier if i build from cources
> and not used the debian package?
>
> Lenz McKAY Gerardo (PICCORO)
> http://qgqlochekone.blogspot.com
Bug#986384: [Courier-imap] courier and maildrop it seems does not work as xpected
Source: courier Severity: grave Justification: causes non-serious data loss I setup both : real system users and virtual ones, both servers have mixed users nature (system ones and virtuals) The specific build removal of the courier-maildrop package breaks the courier MTA utilizing the virtual accounts tools, noted that some variables are imported that normal build of maildrop does not! (I compared the rules files of both), those are HOME, SHELL, LOGNAME and MAILDIRQUOTA while the standalone version won't. MArkus.. i revised and checked related bugs in debian and it seems that standar "maildrop" package is a piece of crap respect of this.. for working i must get back the older courier-maildrop and builds my own package from courier sources, can you get back the build of courier-maildrop i remember that i previously send a request about this! SAM: but,i cannot understand pretty well .. we need to clarify this cos i try to reproduce and i dont know if this was the problem, i do not set any sticky bit in home users.. but my home users are under a subdirectory.. maybe this can be misinterpreted? i found this problem randomly in newer versions of debian packages (i try to compile from sources and i do not have such problem) and in one particular scenery ALWAYS are reproducible: a) server are in a migration of ip and upgrading of programs b) there's some dynamic deliveries pending c) mail queue has almost 200 thousands of pending mails When I changed the DNS to the new server with exact configuration, but another ip, mails are delivered in log and courier system, but if you use lasted maildrop debian shit it does not work! all the new mails are delivered and dissapears (are in queue only but log as delivered) El dom, 4 de abr. de 2021 a la(s) 12:04, Sam Varshavchik ( mr...@courier-mta.com) escribió: > PICCORO McKAY Lenz writes: > > > I have installed maildrop (no longer courier-maildrop) and I am > surprised to > > find that the mails are not arriving at Maildir user place, even > > at /var/mail/spool/$USER file! . that's i ask here to you guys cos i > dont > > know if the problem is dropmail debian package (build separately puff) > or > > courier.. > > It's a long-standing problem with the debian package. > > > I define correctly the maildellivery in imap etc etc but I notice that > the > > mail is in /var/spool/mail instead of in the user's home... and I > already > > defined in /etc/maildroprc the DEFAULT > > Except that the standalone maildrop build is not going to know what the > DEFAULT is, without the appropriate -d option. > > I do not remember any more details, this problem comes up every once in a > while. > > ___ > Courier-imap mailing list > courier-i...@lists.sourceforge.net > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap >
Bug#983478: FAM and other arch/kernels
El mié, 31 de mar. de 2021 a la(s) 09:08, escribió: > > On Wed, Mar 31, 2021 at 08:30:24AM -0400, PICCORO McKAY Lenz wrote: > > linux is so popular (wh ugh) today.. but only for enterprices.. i do > > not see any help for normal users that wants more freedom .. sad and > > oscure! > > Please go away troll. Lest make omise case of some non usefull "please do" guys.. .. but i'm aware of the alternatives on lighttpd cos its my default wegbserver in ALL my services FAM was removed from almost all of the today's software including COURIER or lighttpd my point is not about that .. is about real collaboration.. we cannot change things that can interfere with the work of others.. of course i taking FAM as a vage example .. but we need more interchange of information when we made changes.. THANKS to all for effors and Markus to improve the courier package , you was so flexible about the last days: listening ! AS MUST BE!
Bug#983478: FAM and other arch/kernels
I have reading the wiki page https://wiki.debian.org/SupportedArchitectures and noted that debian drop some time ago the "universal" in their tittle.. just by this kind of SH*T (like systemd and removal of fam by gammon -> so linux only here) my point is that collaboration is D R O P P E D for others.. by preferences on gamin/shitsemd those arches are more close to the abyss .. well all the non-linux arches are "unnofficial" just after becomes official release in wheezy.. >Given courier-imap had several issues in the past with FAM (see #357769, >#578937, #599682), I think it's actually safer to just depend on (and >build against) gamin, instead. I certainly run courier-imap on gamin >exclusively on my systems. lighttpd and courier of course works with gamin but of course this change does not help others mantainers.. i runs kfreebsd in one laptop difficulty due all of those changes.. linux is so popular (wh ugh) today.. but only for enterprices.. i do not see any help for normal users that wants more freedom .. sad and oscure! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#357769: please close #357769 is ancient and is not makes sense now
fam is removed from so please mark as solvet in lasted release! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#985705: courier-authlib: upgrades broken due the move of the tools
El lun, 22 de mar. de 2021 a la(s) 09:57, Markus Wanner (mar...@bluegap.ch) escribió: > > On 22.03.21 14:10, PICCORO McKAY Lenz wrote: > > dpkg: error al procesar el archivo > > /var/cache/apt/archives/courier-authdaemon_0.71.1-2_i386.deb > > (--unpack): > > intentando sobreescribir `/usr/sbin/authenumerate', que está también > > en el paquete courier-authlib 0.71.0-1 > > dpkg: considerando la desconfiguración de courier-authdaemon, ya que > > lo rompería la instalación de `courier-base' ... > > thanks for your report. That surprises me, because I did add: > maybe Andrey are right! i installed the 0.71.0 in stretch from testing and is not a common case.. i guess that i upgraded but debian_release was not complety upgraded, i dont know if this bug report can be closed of let opened for non common cases.. please feel free to address as you guess more after try a clean stretch install and test upgrade to buster and later to testing and it works.. i stored the older vmware image and test again and i canot upgrade.. i guess is a specific case of apt cache.. not of courier-lib .. i must sleep for a while.. thanks for pay attention..
Bug#985705: upgrading from buster to testing it works but not from stretch
trey new case.. upgrading from buster to testing noerrors.. but from stretch i cant upgrade.. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#985705: courier-authlib: upgrades broken due the move of the tools
Package: courier-authlib Version: 0.71.0-1 Severity: serious i just try the upgrade case from stretch to lasted and got error due movement of the tools: as changelog said;: * Move binaries autpasswd, authtest, and authenumerate from courier-authlib to courier-authdaemon. They require the daemon to run and are useless without it. when i try to upgrade got this error: dpkg: error al procesar el archivo /var/cache/apt/archives/courier-authdaemon_0.71.1-2_i386.deb (--unpack): intentando sobreescribir `/usr/sbin/authenumerate', que está también en el paquete courier-authlib 0.71.0-1 dpkg: considerando la desconfiguración de courier-authdaemon, ya que lo rompería la instalación de `courier-base' ... Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#985329: solved upgrading to experimental
Noted with thanks., i search previously before sending and find those two others already marked as grave.. i did not find how this happened again.. i upgraded 4 servers and only two failed.. maybe those have some kind of updates but i do not have the history anymore to check where it was.. so feel free to close this cos was a very big upgraded case, not so common Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com El mar, 16 de mar. de 2021 a la(s) 04:46, Markus Wanner (mar...@bluegap.ch) escribió: > > Control: tags -1 + moreinfo > Control: severity -1 normal > > On 16.03.21 05:46, PICCORO McKAY Lenz wrote: > > i have older packages yet in my install, i dont know how happened.. > > but do not close this bug until i found why happened > > > > after check and forces proper upgraded in xperimental.. is working > > please properly identify the bug you intend to report before filing it > as grave, potentially marking the package as unfit for release. > > Regards > > Markus
Bug#985329: solved upgrading to experimental
i have older packages yet in my install, i dont know how happened.. but do not close this bug until i found why happened after check and forces proper upgraded in xperimental.. is working Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#985329: courier-mta not startable/configurable due mkesmtpdcert
Package: courier-mta Version: 1.0.16-3 Severity: grave Justification: renders package unusable i guess real reason of bug #984696 and #984694 is that the mkesmtpdcert tool has an error: check this sequence: it seems that the script put the pem file in the /usr/lib/courier event in /etc/courier, or maybe permission problems serveruno:/etc/courier# mkesmtpdcert /etc/courier/esmtpd.pem already exists. serveruno:/etc/courier# rm /etc/courier/emstpd.pem rm: no se puede borrar '/etc/courier/emstpd.pem': No existe el fichero o el directorio serveruno:/etc/courier# Markus.. the problem is not the smtpaccess.dat or imapaccess.dat so please check this again .. just run the script .. if you could reproduce it.. mark #984696 and #984694 as real solved i m still coding at the scripts but i just testing first upgrade xperience.. (i never do upgrade .. just one install and 9 years of peace since squeeze) Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#984810: courier-authlib: authtest can access user data information from normal users accoun
El lun, 8 de mar. de 2021 a la(s) 14:56, Markus Wanner (mar...@bluegap.ch) escribió: > not very different from a `cat /etc/passwd`). but we can use the tool to parse brute force attacks in combination with authpasswd tool that is also another case of! so an important update for oldstable, stable and future next release must be addressed as i xplain!
Bug#984810: [courier-users] any request using authtest are normal
thanks for clarifications Alessadro. but it seems easy if we look from the socket directory access, but .. > The socket file is srwxrwxrwx root root in both cases, but the parent > directory > on the locally built server is: > drwxr-x--- courier courier authdaemon > whilst on the Debian server it is: > drwxr-xr-x courier courier authdaemon anyone that have directory access wil can use authtest.. in debian is just a extra 755 but so any user that have access to courier group will get information.. still are a hole security so authtest must be acceded only by admins users.. or i mean only by root and courier users i changed and suggest the authtest and any other admin tool must be only accessed by root and courier user! > > > hth > Ale > -- > > > > > > > > > > > > > > > > > > > > > > > > > > ___ > courier-users mailing list > courier-us...@lists.sourceforge.net > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
Bug#984810: courier-authlib: authtest can access user data information from normal users accoun
Package: courier-authlib
Version: 0.71.0-1
Tags: upstream security buster stretch bullseye
Justification: user security hole
Severity: grave
Usertags: security
The /usr/sbin/auth is a program that can test from a
installation setup if authlib daemon are working
without the complete courier suite installed
(for cluster or distributed environment as i made it)
Currently as normal user, it can be accessed
to users database if we setup mysql, postgres
or sqlite, inclusively ldap setups.. i mean,
a limited account can query users mail data
to made some kind of attack
This information is reveal from DB:
serveruno:$ authtest test
Authentication succeeded.
Authenticated: test (uid 244, gid 244)
Home Directory: /home/users/intranetusers/test
Maildir: /home/users/intranetusers/test/Maildir
Quota: (none)
Encrypted Password: {MD5RAW}34ca4238a0b923820dcc509a6f75849b
Cleartext Password: 1
Options: (none)
Of course clear password is a good practice do not store ..
but in intranets and corporate environments
knowed password are mandatory due management
of users..
In any case, this information is too open,
We used the authpasswd to check users db
setup is working on changes and upgrades
For this upgrade from a stable installation
to proper test lasted version before send this report,
the problem is present in all the versions of debian
packaged
I asked to upstream but is so obvious this problem
so i send to Debian,a sense solution is limit the
access to program (what i do):
chmod 750 /usr/sbin/authtest
chown courier:root /usr/sbin/authtest
i already ask to upstream but i dont know what SAm will think about it!
ADDITIONAL NOTE: the package that own the program is authlib.. this
is completely wrong.. cos important setup is not retrieved by
reportbug like the authdaemon setup files modified.. the
/usr/sbin/authenumerate /usr/sbin/authpasswd and /usr/sbin/authtest
must belong to authdaemon (to make sense)
Kernel: Linux 5.10.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages courier-authlib depends on:
ii adduser 3.118
ii libc6 2.31-9
ii libgcc-s110.2.1-6
ii libgdbm61.19-2
ii libltdl72.4.6-15
ii libpam0g1.4.0-6
ii libstdc++6 10.2.1-6
Versions of packages courier-authlib recommends:
pn expect
courier-authlib suggests no packages.
-- no debconf information
Bug#983786: affects to bullseye too
The relevant commit is 2ebfa0325b501e308e43b451561a06cb18bb28ec (1) in the courier-libs repo. But i'm afraid that backporting to bullseye will need another more big commit, i'm asking to SAM for.. [1] https://github.com/svarshavchik/courier-libs/commit/2ebfa0325b501e308e43b451561a06cb18bb28ec Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com El lun, 1 de mar. de 2021 a la(s) 18:03, PICCORO McKAY Lenz ( mckaygerh...@gmail.com) escribió: > Source: courier > Version: 1.0.14-2 > Severity: serious > > hi markus.. sorry but this bug also affected freeze released bulleye.. > but noted that the commit is a changelog only entry.. so i asked to > SAM > > > https://sourceforge.net/p/courier/mailman/courier-users/?viewmonth=202103=1 > > so this bug is closed only for uinstable but not for freeze testing > bullseye > > -- > Lenz McKAY Gerardo (PICCORO) > http://qgqlochekone.blogspot.com >
Bug#983786: affects to bullseye too
Source: courier Version: 1.0.14-2 Severity: serious hi markus.. sorry but this bug also affected freeze released bulleye.. but noted that the commit is a changelog only entry.. so i asked to SAM https://sourceforge.net/p/courier/mailman/courier-users/?viewmonth=202103=1 so this bug is closed only for uinstable but not for freeze testing bullseye -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#983478: some hints to take in consideration
> Incorrect information was given in #981513: > - the release team has now decided that fam will stay in bullseye, > it is expected that fam will be removed for bookworm that's true.. some ports need fam cos gamin is linux only.. and remenber that debian it build for others kernel/archs combinations! and also future releases of courier it seems will deprecated fam/gammin dependency.. sorry MArkus but fam must be listed as first and gamin as optinoal.. so:" fam | gamin " in imap package and build depends on libfam-dev | libgamin-dev -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#983786: fix crash caused by a malformed DNS query/response.
Source: courier Version: 1.0.15-1 Severity: serious already upstream in Fixes a crash caused by a malformed DNS query/response. in details: backporting this: https://github.com/svarshavchik/courier/commit/91b3f7ca6c38c9b56c93484f8687c99d6c62c091 -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#983201: new build dsc
I build new packages for iperf2 if someone DM interested just parsed and tuned it for debian: https://build.opensuse.org/package/show/home:vegnuli:deploy-vnx2/iperf2 Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#983201:
Package: iperf Version: 2.0.14a+dfsg1-1 Severity: important Tags: upstream iperf now has a new version (iperf) 2.1.0rc that has some improvements and several fixed.. current debian version has two critical bugs that reports incorrect numbers #965974 and #760590 makes the package acts like a toy cos cannot be used in production environment (we are not under little router guys) i package a new version at the vegnuli OBS deb repository if some one want to take a look and improved for debian, it seems mantainers are sleeping since a long time Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#965974: patch available but still happened!
this but has time.. there-s still happened today? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#959174: php-fpm and others init systems
what is the status of this? when i disabled the systemd and try to use php-fpm it breaks and does not run.. > ... we feel important to urge the php-fpm maintainers to work constructively > to find a suitable way to describe the needed dependencies so that php-fpm > can be installed in a containerized system without a full init system. is clear the hostile response since the first mensaje and the amount of users there that respons! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#982797: too much preference for apache2
the offending part is :; > For this we will add "Recommends: libapache2-mod-php (= X) | php-fpm (= X) | > php-cgi (= X)" to the php package. X is here the binary version of the > package which is easy as they are all built from the same source package. this has at first the "libapache2-mod-php" that is incompatible with php-fpm the demanding today preferred and well agnostic with all the webservers.. in almos all of the php package the apache2 module is first and "prefered" but its almost the less used! we are in the 21th century and fpm is the demanding now! lighttpd and ningx is the rule! and h2o is comming Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#982574: current php stable crash after configuring
El sáb, 13 de feb. de 2021 a la(s) 12:29, Ondřej Surý (ond...@sury.org) escribió: > > this problem is present in debian stable, also in php 7.0, it makes > > php7.0 is not part of any supported Debian release. Debian 9 stretch umm and this is the mantainer? dont know what debian php packages are supported? > And yet, this is the first time somebody ever reported this feature > request in Debian. Cos you said in github that REPOS ARE IN DEBIAN! so you use your debian work for your own fame? > > That would be against Debian policy. The PHP already gets a preferential > treatment since stable Debian gets new upstream releases, but changing > the configuration options within the stable release would be very frowned > upon. I understand the case... this is a problem that was more accentuated with the virtualbox debian package, i understand that! but is not the case here.. the problems in debian packages is that the maintainers don't know complete the packages they managed.. and debian has a strong policy about that, pretty ironic.. by example you are the php debian mantainer, and dont activate that ACL feature since what? also php-http of oldstable have problems but people just ignored to send debian mails cos dont understand the bug system (mails only) and now confused the sury repos with debian ones .. > > > i was also blocked for saying what it is... > > In my personal space, I block people who are rude to me or act in entitled > way demanding stuff and not being able to step back. so if are your personal one.. but use the debian git, incusive debian git has a branch with "sury" word.. interesting! i remenber the case of marillat repos! in that case debian ask to marillat to remove many things.. but what about sury repos? umm very interesting that now freexian will have a very xpensive repos with php only umm
Bug#982574: current php stable crash after configuring
Package: php7.3
Version: 7.3.19-1~deb10u1
Severity: important
Tags: functionality
this problem is present in debian stable, also in php 7.0, it makes
the package unusable in shared environment by different webservers in
a cloud configuration, that if it is possible in other distros like
alpine, it should also be fixed in 7.3 which is supported in debian
i was also blocked for saying what it is... this bug and many others
happened in the php debian packages , the packages in debian have
several segfaults and crashes due to the fast paced way of going on
the newest, (and when the maintainer is treated as he treats others
("work for me", remenber it) then he blocks people in gitlab, but
links the git repo to the debian one saying the work is in debian so
where are the bugs sent to? acl fails also in all php debian packages.
tdenetwork of devuan repos and me, rebuilts the packages and none of
these bugs happened, we made some adjust and try to said but reports
were ignored like #962495 and #959042
i guess sury repos must have their own git separate from debian and do
not mess with debian quality work
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Bug#980883: fix uninitialized var
Package: src:courier-unicode
Version: 2.1-3
Severity: important
Tags: buster
Description: BUGFIX unicode::iconvert::convert, fix uninitialized
variable. (already soved in bullseye 2.2 but not in stable)
Origin: upstream,
https://github.com/svarshavchik/courier-libs/commit/181c424a834d13a27e6026d4d05ac49230372aba#diff-2fcf76a4c3c75b1fb5288d83d62dd114dc556d16fba206ab35d38bfe294a2857
--- courier-unicode-2.1.orig/unicodecpp.C
+++ courier-unicode-2.1/unicodecpp.C
@@ -180,7 +180,10 @@ std::string unicode::iconvert::convert(c
int err;
if (uc.empty())
+ {
+ errflag=false;
return buf;
+ }
if (unicode_convert_fromu_tobuf([0], uc.size(),
dstcharset.c_str(), , ,
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Bug#980881: courier unicode cone lib bugfix
Package: src:courier-unicode
Version: 2.1-3
Severity: important
Tags: buster
Usertags: cone
backport important bug agains cone in stable current release: Fix bug
triggered by cone. Parameters to memmove were reversed. len is the
size of the buffer. len-pos-cnt characters were copied in error to
position pos+cnt. As such this did not overflow. I.e. if len was 8
(eight chars), pos was 1 and cnt was 2, then 8-2-1=5 characters were
copied to offset 3, right at the end of the buffer. This was just
plain wrong.
Origin: upstream,
https://github.com/svarshavchik/courier-libs/commit/b89f5f8dc09431bb345308b3a0ffd5f7d22cdfb2#diff-2fcf76a4c3c75b1fb5288d83d62dd114dc556d16fba206ab35d38bfe294a2857
--- courier-unicode-2.1.orig/unicodebuf.c
+++ courier-unicode-2.1/unicodebuf.c
@@ -89,7 +89,7 @@ void unicode_buf_remove(struct unicode_b
cnt=p->len-pos;
if (cnt)
- memmove(p->ptr+pos+cnt, p->ptr+pos, p->len-pos-cnt);
+ memmove(p->ptr+pos, p->ptr+pos+cnt, (p->len-pos-cnt) * sizeof(char32_t));
p->len -= cnt;
}
--- courier-unicode-2.1.orig/unicodetest.c
+++ courier-unicode-2.1/unicodetest.c
@@ -123,11 +123,30 @@ static void test2()
exit(1);
}
+void testunicodebuf()
+{
+ struct unicode_buf buf;
+
+ unicode_buf_init(, -1);
+ unicode_buf_append_char(, "01234567", 8);
+ unicode_buf_remove(, 1, 6);
+
+ if (unicode_buf_len() != 2 ||
+ unicode_buf_ptr()[0] != '0' ||
+ unicode_buf_ptr()[1] != '7')
+ {
+ fprintf(stderr, "unicode_buf_remove failed\n");
+ exit(1);
+ }
+ unicode_buf_deinit();
+}
+
int main(int argc, char **argv)
{
const char *chset=unicode_x_imap_modutf7;
int argn=1;
+ testunicodebuf();
if (argn < argc && strcmp(argv[argn], "--smap") == 0)
{
chset=unicode_x_imap_modutf7 " ./~:";
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Bug#979816: error also in stable if only sysvinit is available!
Package: courier-authdaemon Version: 0.66.4-9 Severity: important confirmed too in debian stable and oldstable, disabling shitsemd courier cannot be installed .. patch already provided: https://salsa.debian.org/debian/courier-authlib/-/merge_requests/2 Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#979816: authdaemon fails in any other init system choice
Package: courier-authdaemon Version: 0.71.0-1 Severity: important courier authdaemon fails to start in any other system cos need directories are not created .. i filed this bug report agains the 0.71.0 but it seems i suspect olders have the same problem.. since the change of https://salsa.debian.org/debian/courier/-/commit/537a612bd8ee2734d830e324479f05c1a97b7f2d (that particulary was a mess ) there's more bugs reported that relies on init scripts since shistemd start to take Debian other package start to lost importance in the diversity of the init systems.. we need to create the /run/courier/authdaemon/ if not.. this is the result: Unpacking courier-authlib (from .../courier-authlib_0.71.0-1_i386.deb) ... Selecting previously unselected package courier-authdaemon. Unpacking courier-authdaemon (from .../courier-authdaemon_0.71.0-1_i386.deb) ... Processing triggers for man-db ... Setting up courier-authlib (0.71.0-1) ... Setting up courier-authdaemon (0.71.0-1) ... [] Starting Courier authentication services: authdaemond/run/courier/authdaemon/pid.lock: No such file or directory ll_daemon_start: Resource temporarily unavailable . ok invoke-rc.d: initscript courier-authdaemon, action "start" failed. dpkg: error processing courier-authdaemon (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: courier-authdaemon E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up courier-authdaemon (0.71.0-1) ... [] Starting Courier authentication services: authdaemond/run/courier/authdaemon/pid.lock: No such file or directory ll_daemon_start: Resource temporarily unavailable . ok invoke-rc.d: initscript courier-authdaemon, action "start" failed. dpkg: error processing courier-authdaemon (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: courier-authdaemon Press Return to continue. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#979545: the stretch-pu: package courier/0.76.3-5+deb9u1 still are broken
Package: courier-mlm Version: 0.76.3-5+deb9u1 Severity: grave Justification: renders package unusable the upload of Andreas from #875696 that backported the "fix" to stretch, is still broken cos package still are unusable.. it never finishes to install cos lists directories missing from configuration never are pre-made.. cos to make a list we need to set up too many things at post install -.-. by example a debostrap always will be broken even if shistemd are used by default and not only sysvinit, check bug #979161 so an urgent backport of the commit https://salsa.debian.org/debian/courier/-/commit/be22539626fcefbcadcfa377454d0e42d6009ade must be done also the shistemd unit file must be installed disabled because of the lists directories missing from configuration Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#979161: webmlm daemon fails cos systemd does not work as old days
El dom, 3 de ene. de 2021 a la(s) 18:25, Markus Wanner (mar...@bluegap.ch) escribió: > Yes, I noticed this as well. Which of these two options do you prefer: > errr again.. sorry but here is only one option.. XD XD XD > * install the systemd service as initially disabled, similar to the sysv > init scripts > this is the only option.. put a note in the postinst .. and don't worry about how to deal with the "complicated" process of mail list creation.. is just a lot of reading of manpages.. that's all. > > Regards > > Markus > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#831366: forward to upstream and ask for patch
forward to upstream and ask for patch https://sourceforge.net/p/courier/mailman/message/37189475/ Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#979161: webmlm daemon fails cos systemd does not work as old days
Package: courier-mlm Version: 1.0.14-1 Severity: normal The (again) systemd does not permit a good installation of mlm cos package does not have (yet) defined at postinst step a list.. so package will fail to install (check the error that said "Missing LISTS setting") becouse the webmlmrc file does not have yet defined that cos obviously doe snot are none mail list made at postinst step In old days of sysvinit the package have a "default" file at /etc/defaults that said does not run yet the daemon and of course does not faill with init scripts Setting up courier-mlm (1.0.14-1) ... Job for courier-mlm.service failed because the control process exited with error code. See "systemctl status courier-mlm.service" and "journalctl -xe" for details. invoke-rc.d: initscript courier-mlm, action "start" failed. ● courier-mlm.service - Courier MLM VNX Daemon Loaded: loaded (/lib/systemd/system/courier-mlm.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2021-01-02 18:21:51 CST; 6ms ago Process: 29063 ExecStart=/usr/bin/webmlmd start /etc/courier/webmlmrc (code=exited, status=1/FAILURE) Jan 02 18:21:51 isomaker systemd[1]: Starting Courier MLM VNX Daemon... Jan 02 18:21:51 isomaker webmlmd[29063]: Missing LISTS setting Jan 02 18:21:51 isomaker systemd[1]: courier-mlm.service: Control process exited, code=exited, status=1/FAILURE Jan 02 18:21:51 isomaker systemd[1]: courier-mlm.service: Failed with result 'exit-code'. Jan 02 18:21:51 isomaker systemd[1]: Failed to start Courier MLM VNX Daemon. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#974979: make courier configuration by default on directories.. event files
El sáb, 2 de ene. de 2021 a la(s) 09:54, Markus Wanner (mar...@bluegap.ch) escribió: > just a matter of defaults. I agree the directories should be created by > default. > > > First setp to solve this is in courier-base package, must be changed > > to true, this will create the minimal set of directories. > If you're speaking of the `courier-base/webadmin-configmode` template > question, I'm with you. This needs to vanish. the question is made in courier-base .. cos webadmin depends on > > Later in a new revision remove the question and migrate to use > > only directories (that can co-exist with normal files), manpages > > of the courier suite points so many times about those directories.. > Manpages should be adjusted to clarify both is possible, IMO. manpages already point that! the html and web of courier is also almost same as manpages! > should be possible. However, I think it already *is* possible now. It > clearly works for me (tm). Anything in specific that doesn't work when > configuring using multiple files in a directory? as i said, manpages said it works for both! so directories must be default, webadmin does not touch single files unless are need!. just need directory structure be present.. > > Regards > > Markus i alreay include some of those direction in the !9 pull request! dont worry about lot of commits.. merge rewuest will be squash wen merged in one only message!
Bug#893839: sqwebmail fix for cache login and right permissions
as of /etc/cron.d/sqwebmail points.. the user that seems own the cache directory of the sqwebmail is "bin" and cos that the cache files for users when no virtual ones are setup (pam, localdb, ldap) cannot be created: Jan 1 23:33:53 isomaker sqwebmaild: LOGIN, user=user, ip=[186.91.0.20] Jan 1 23:33:53 isomaker sqwebmaild: maildircache: Cache create failure - unable to create file /var/cache/sqwebmail/223550/us/user. solution seems easy and no security will implicate here: in sqwebmail.postinst line 68: add_override courier bin 0770 /var/cache/sqwebmail and in sqwebmail.prerm line 51: del_override courier bin 0770 /var/cache/sqwebmail This was explained in the pull !9 README.Debian of the courier git work and i will added that patch to the merge request. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#974979: make courier configuration by default on directories.. event files
Currently Courier uses several configuration files in /etc/courier that can be replaced by a subdirectory whose contents are concatenated and treated as a single, consolidated, configuration file. This behaviour is less confused for the few tutorials and works better to manipulate the files by scripts (as webadmin cgi does) First setp to solve this is in courier-base package, must be changed to true, this will create the minimal set of directories. Later in a new revision remove the question and migrate to use only directories (that can co-exist with normal files), manpages of the courier suite points so many times about those directories.. by example the esmtpacceptmailfor: can be a single file in the path /etc/courier/esmtpacceptmailfor of a directory at the path /etc/courier/esmtpacceptmailfor.dir and all files inside will be parsed as single one. better example is hosted domains, can be a single file in /etc/courier/hosteddomains but is better a directory /etc/courier/hosteddomains and each domain could be a single file (named as the domain without dots) and with domain inside in plain text. as i said.. this behaviour is more elaborated but more organized for huge servers like production real cases Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com El jue, 31 de dic. de 2020 a la(s) 05:58, Markus Wanner (mar...@bluegap.ch) escribió: > > Control: tags -1 +moreinfo > Control: severity -1 normal > > Hi, > > from this wording, I have no idea what this bug is about, sorry. Please > clarify your proposal. > > Markus
Bug#215360: patch already merged upstream so close #215360
Please close (not only archive) this bug #215360 cos as https://sourceforge.net/p/courier/mailman/message/37186787/ was merged long time ago for sqwebmail, so any recent version is fixed now! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#978718: readme file in courier-base still has confused lines
Package: courier-base Version: 1.0.14-1 Severity: important the courier-base README.Debian file is badly formatted and has missing important info not reflected. bug report #974585 : was closed in 1.0.14-1 but the README.DEbian file still points that the "error" are hidden! what? i pointed that also.. the file could produce confusion about if there's some problems if FAM are not running and the admin read that line! i send a pull request for that .. each pull request (stupidly) it takes so much time to work cos i have very limited connection so i hope you read all the mails too Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#755092: soscks5 support needs hole recompilation and new package
This depends of a new package to made in debian: Courier Socks 5 Proxy client library, which allows Courier to send outgoing mail using a Socks 5 proxy. This means need to convert or merge this bug request in a RFP of the Courier Socks 5 proxy before building Courier in order to use a Socks proxy to send outgoing mail. FEATURES: 1. Courier-mta is the only suite that can use a socks5 to delivery to a different network 2. Access control: define IP address ranges allowed to proxy through the server. 3. Access control: import list of banned IP address range, in the P2P file format. A "socksify" application wrapper script, that uses shared library tricks to try to redirect network connections from standalone application through the Socks 5 proxy server. http://www.courier-mta.org/download.html#sox Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#341205: README's highly confused and wrong configurations
Mark I have decided to send this email to all 5 bug reports at the same time because they deal with the same topic: a rather confusing reading file and a configuration out of all logic in the courier-webadmin and sqwebmail packages, i just try to make the pull request for the changes required.. PLEASE read here: first of all the new apache2 config file for sqwebmail causes problems with path for static files, sqwebmail expected to find css file in /sqwebmail/sqwebmail.css but i got a http 500 error cos xtrange cgi configurations automatically made by package.. those must be erased and admins must fine tune by is own hand in each case if want hide path in urls, that's could be the reason of the question in debconf about copy or symlink, although the apache script limits access the cgi can still be accessed and there is no real security here bug report #190725 : config web for courier-webadmin and sqwebmail are all wrong, packages assumes apache2 (most inefficient web server), a bad taste, bug that's not the problem: the sqwebmail case config file said "allow only local" but is nonsense because the security is configured by a build time configuration: https://redmine.lighttpd.net/issues/304 3 times bad made the package make this unusable by confusion bug report #190725 : in same topic: the localhost build in restriction of the courier-webadmin is another very confused setting for the admin! so we should leave this alone and provide example files as it has always been in Debian bug report #126735 and #341205 : in same topic: default installation is not explained (respect the courier documented) and there's no Debian document that points the difference.. neither a document of debian way and the differences.. same case of the #190725 about #341205 i will send that patch to upstream but a README file must sove the situation for now.. this patch is trivial and must be revised cos is old about #910527 #910529 : was merged but not property explained in NEWs or README. the current courier-base pointing about the new permissions but does not said nothing about the upgrade problem that still persist and inclusively seems is also cited in the postinst script https://salsa.debian.org/debian/courier/-/merge_requests/9 https://salsa.debian.org/debian/courier/-/merge_requests/10 Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#578937: FAM must be depend
after read carefully gamin uses inotify, this becomes a question whether the underlying filesystem supports inotify. it depends hardly on linux-specific things fam is more unix standar way and more classical.. old school powered.. also upstream points that FAM/gamin must be installed to property work.. of course is not a software that comes or forced the usage of but that does not mean is not a dependency Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#971385: important error and patch provided
it happened to me and find the reason now.. but i upgraded from debian 6 to 7 and later to 8 then to 10.. well this is a bug that already has solution and is important! as i pointed i upgrade to debian 10; and in debian 6 works perfectly .. and in this particular bug 971385 reporter saids that debian 9 works.. (that's the reason of Debian 10 sh**t many other packages already have problems) Markus you mail me that "help providing patch" but later i said "read the mails" .. and you said "i cannot be". . also it points that trying to recompile the package it does not integrate to default cos the COMPLICATED sys-v init crips and also the changes not property documented in the changelog respect the upstream.. README.Debian files only has minimal information and tutorial of well documented package does not works Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#584126: pain in ass cos depends on "default-mta"
this is another problem when sysadmin wants to install courier-suite.. the change is simple no pacht need just maintainer attention.. change courier package depends in : courier-pop courier-imap of course those packages can work with other mail suite but default (as just apt-get install does) install doe snot handle that! so dependences are wrong in all way! Depends: courier-mta | default-mta | mail-transpor-agent Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#933948: too many split f the same things
El dom, 27 de dic. de 2020 a la(s) 12:42, Markus Wanner (mar...@bluegap.ch) escribió: > On 12/27/20 5:22 PM, PICCORO McKAY Lenz wrote: > > > it seems has several inter-dependencies.. or as you mantainers called > > circular dependences.. so i'm unable to check in production cos does not > > buil in a OBS environment.. > > I see no circular dependency here. Register to review is a pretty > simple one-way dependency. > there's a debian issue already send about that but i'm too complicated for.. i'm searching for.. but i cant find it yet! and was marked as important.. it seems related to systvinit .. but i cant find it yet > Glad you begin to understand that packaging is not quite as trivial as > compiling from source for just your local installation. > of course.. we need to improve to property give more feedback to the today quality of.. remember that today's sysadmins does not have same skill that old school .. that's why system-ht are handle right? so easy to use for thems! XD XD > > Regards > > Markus >
Bug#922199: duplicate
ducplicate of 922199 922200 this is not a courier bug.. is a debian problem cos merging file system migration.. please considering olders one.. and does not hardcoded the path as solution also please document that in debian README cos debian package are so confused now to property configured respect upstream that already works Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#436266: some miscunderstands
1. when set to "IMAP_EMPTYTRASH=" it default to 0 so all the mail are deleted of course.. is not important but of course an misc on code.. but this are from 2017 so must be recheck with recent versions.. of course i canot test with debian package cos does not build property 2. reported does not know what are doing.. when ask if all mail are moved to trash with some sets of configuration doe snot know what are talking about.. also does not read the hole documentation.. neither set the IMAP_MOVE_EXPUNGE_TO_TRASH var property or IMAP_EMPTYTRASH variable in a high number. the only bug here is when there's no definition for IMAP_EMPTYTRASH= but is a minor bug.. sysadmin or reported does not read property at documentation or standard .. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#933948: too many split f the same things
the review needs registration etc etc.. i try to analize but it has too complicated things for quick review.. it seems has several inter-dependencies.. or as you mantainers called circular dependences.. so i'm unable to check in production cos does not buil in a OBS environment.. again as i mailed.. more complications.. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#968038: since that common script some problems with unkow args
i have this problem and some others.. this is an extra problem since adopted that common part: root@isomaker:/# /etc/init.d/courier-mta statussdzd /lib/init/init-d-script: line 113: .: statussdzd: file not found root@isomaker:/# service courier-mta statussdzd /lib/init/init-d-script: line 113: .: statussdzd: file not found Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#974898: new release upstream fixed several problems
the changelog does not take in consideration the amount of bugs reports.. seems do not read all ( i read all the issues, inclusively ask some to upstream and read carefully about the maildrop hole issue) also there's a new unicode release that fixed the BROKEn cone package that are not taken in consideration El jue, 26 de nov. de 2020 a la(s) 09:40, Stefan Hornburg (Racke) (ra...@linuxia.de) escribió: > > On 11/26/20 1:47 PM, PICCORO McKAY Lenz wrote: > > seems do you not read the mails, several issues are solved upstream, > > but still are happened cos there's no new release. (not so difficult > > to make it) > > > > same for courier, several bug reports are not taken in consideration > > (solved of course) and now today make a separate package for maildrop > > is nonsense cos is part of courier-mta suite.. it belongs to that > > suite, but upstream committed some of the requested features > > The question is what the plan of the current maintainer is. He did > some work here: https://salsa.debian.org/debian/courier, but didn't do > an upload since the beginning of 2019. > > Regards >Racke > > > > > El jue, 26 de nov. de 2020 a la(s) 07:56, Josip Rodin > > (j...@debbugs.entuzijast.net) escribió: > >> > >> > >> Why are you posting these agitated bug reports? Can I suggest that you > >> first > >> calm down and try to compose your thoughts, and then put that in writing > >> while bearing in mind that an assumption of good faith is the only proper > >> way to operate? > >> > >> On Mon, Nov 16, 2020 at 04:08:21AM -0400, PICCORO McKAY Lenz wrote: > >>> Package: maildrop > >>> Version: 2.9.3-2 > >>> Severity: important > >>> > >>> The maildrop package in debian is severely out of sync and outdated: > >>> > >>> First of all stop of "Upstream is not willing to add another feature", > >>> seems people dont understan maildrop are made for courier, and if need > >>> can proposed a fork for that! > >>> > >>> Second: **several problems where aborted upstream**, the most > >>> important ones are: > >>> * libs/maildrop/deliver.C (delivery): Always return 75 upon > >>> delivery failure, for the standalone maildrop build. related to #481223 > >>> * libs/maildir/maildirmake.c (main): maildirmake's -q option > >>> will create the maildir if it does not exist. related to #501557 > >>> * libs/rfc2045/reformime.c (main2): Fix crash when the -s option is > >>> not valid. related to #71625 > >>> * rfc2045/reformime.c (main2): fix crash if -x or -X is specified > >>> without the corresponding -s option. related to #71625 > >>> > >>> A new maildrop pack is required and this must either come from the > >>> same courier sources (#867121) or update the one... this last seems > >>> quite stupid as courier is the official sources of maildrop and > >>> although it is offered separately by the author upstream, unifying it > >>> will improve maintenance from a team, and as you guys notice lack of > >>> interest/avaliable time in the courier suite (reading the last > >>> changelog, seems changes are more to complain with debian package > >>> policy that is innecesary respect real issues) > >>> > >>> ... and as far as I can see you are looking for the sources in sf > >>> instead of the right place which is the courier oficial download page, > >>> additional while the courier-mta sources are up to date in > >>> salsa-debian, the maildrop one in salsa-debian are too old respect the > >>> mta suite! > >>> > >>> while I made my own package on OBS vegnuli home for Devuan and Debian, > >>> is you guys need help i'm a often user of the complete suite and not > >>> just parts or toys of, maildrop can be build with two ways: > >>> * set GID mail without restricted caller (maildrop) > >>> * set UID root with restricted caller for courier-mta > >>>(maildrop-courier) -- missing and the way i set in my package cos > >>> is the need by the original suite the courier-mta > >>> > >>> > >>> NOTE: Courier maildrop in debian present a very not proper behaviour.. > >>> original sources are from courier and any other implementation are > >>> non-related and users can fork the software, cases like #375589 are > >>> not valid cos seems maildrop (as author make it for courier
Bug#974898: new release upstream fixed several problems
seems do you not read the mails, several issues are solved upstream, but still are happened cos there's no new release. (not so difficult to make it) same for courier, several bug reports are not taken in consideration (solved of course) and now today make a separate package for maildrop is nonsense cos is part of courier-mta suite.. it belongs to that suite, but upstream committed some of the requested features El jue, 26 de nov. de 2020 a la(s) 07:56, Josip Rodin (j...@debbugs.entuzijast.net) escribió: > > > Why are you posting these agitated bug reports? Can I suggest that you first > calm down and try to compose your thoughts, and then put that in writing > while bearing in mind that an assumption of good faith is the only proper > way to operate? > > On Mon, Nov 16, 2020 at 04:08:21AM -0400, PICCORO McKAY Lenz wrote: > > Package: maildrop > > Version: 2.9.3-2 > > Severity: important > > > > The maildrop package in debian is severely out of sync and outdated: > > > > First of all stop of "Upstream is not willing to add another feature", > > seems people dont understan maildrop are made for courier, and if need > > can proposed a fork for that! > > > > Second: **several problems where aborted upstream**, the most > > important ones are: > > * libs/maildrop/deliver.C (delivery): Always return 75 upon > > delivery failure, for the standalone maildrop build. related to #481223 > > * libs/maildir/maildirmake.c (main): maildirmake's -q option > > will create the maildir if it does not exist. related to #501557 > > * libs/rfc2045/reformime.c (main2): Fix crash when the -s option is > > not valid. related to #71625 > > * rfc2045/reformime.c (main2): fix crash if -x or -X is specified > > without the corresponding -s option. related to #71625 > > > > A new maildrop pack is required and this must either come from the > > same courier sources (#867121) or update the one... this last seems > > quite stupid as courier is the official sources of maildrop and > > although it is offered separately by the author upstream, unifying it > > will improve maintenance from a team, and as you guys notice lack of > > interest/avaliable time in the courier suite (reading the last > > changelog, seems changes are more to complain with debian package > > policy that is innecesary respect real issues) > > > > ... and as far as I can see you are looking for the sources in sf > > instead of the right place which is the courier oficial download page, > > additional while the courier-mta sources are up to date in > > salsa-debian, the maildrop one in salsa-debian are too old respect the > > mta suite! > > > > while I made my own package on OBS vegnuli home for Devuan and Debian, > > is you guys need help i'm a often user of the complete suite and not > > just parts or toys of, maildrop can be build with two ways: > > * set GID mail without restricted caller (maildrop) > > * set UID root with restricted caller for courier-mta > >(maildrop-courier) -- missing and the way i set in my package cos > > is the need by the original suite the courier-mta > > > > > > NOTE: Courier maildrop in debian present a very not proper behaviour.. > > original sources are from courier and any other implementation are > > non-related and users can fork the software, cases like #375589 are > > not valid cos seems maildrop (as author make it for courier filtering) > > is a courier implementation if applies! so any external specific usage > > are purely optional > > > > This are related to #910380 (separate makemime from sources) #204187, > > #596057 & #375589#26 (bad usage cos is not made for), #481223 > > (changed behaviour cos is not made for, what?), #592585 (dovecot > > specific crap) and go and go.. seems people thinks that maildrop are > > made for others rather than the courier suite... funny please close > > all of those package cos seems many of them are not supported by > > upstream and community must make a fork in those several cases! > > > > Lenz McKAY Gerardo (PICCORO) > > http://qgqlochekone.blogspot.com > > -- > Josip Rodin
Bug#481223: dsc and sources if interested: we need new release
for those interesting (cos seems mantainers dont care of courier packages) https://build.opensuse.org/package/show/home:vegnuli:deploy-vnx1/maildrop buils and dsc source files for all debians .. including 10 and testing, and stop to said "that is for olders" dont be stupid * New upstream release: Closes #974898 + Closes: #204187, #596057, #375589, #481223, #592585 + Closes: #501557, #481223, #716252 + Updated config file Closes: #861906 * debian/control: + new dependency libidn-dev | libidn11-dev * debian/patches: - remove 0003-permanent-err.patch merged upstream. Closes: #265399 + Explicit pass CAT=/bin/cat to configure to make build reproducible between merged-usr and non-merged-usr systems. Closes: #915180 + refresh the Re-added the fix for #82986 Filter directory and files being accessible to groups and just check for world-writability. + refresh 0004-deliver-extra-newlines.patch, just comment! -- PICCORO Lenz McKAY Tue, 17 Nov 2020 10:19:26 -0400 and no: i not use debian mentors cos i do not have my own network connection so i must upload in a web browser my files so that's why i used obs Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#974979: make courier configuration by default on directories.. event files
Source: courier Severity: important directory configuration behaviour produces a better way of manage courier, we need to simplified the management of the package also directory behaviour is more easy to manage for people just by addidinjg files per host name.. inclusively manpages refers in that way the only offers to that is in the courier-webadmin package and there's no mention of the behaviour at the README of courier-base package but almost in all the manpages that may confuse --- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#974898: new release upstream fixed several problems
Package: maildrop Version: 2.9.3-2 Severity: important The maildrop package in debian is severely out of sync and outdated: First of all stop of "Upstream is not willing to add another feature", seems people dont understan maildrop are made for courier, and if need can proposed a fork for that! Second: **several problems where aborted upstream**, the most important ones are: * libs/maildrop/deliver.C (delivery): Always return 75 upon delivery failure, for the standalone maildrop build. related to #481223 * libs/maildir/maildirmake.c (main): maildirmake's -q option will create the maildir if it does not exist. related to #501557 * libs/rfc2045/reformime.c (main2): Fix crash when the -s option is not valid. related to #71625 * rfc2045/reformime.c (main2): fix crash if -x or -X is specified without the corresponding -s option. related to #71625 A new maildrop pack is required and this must either come from the same courier sources (#867121) or update the one... this last seems quite stupid as courier is the official sources of maildrop and although it is offered separately by the author upstream, unifying it will improve maintenance from a team, and as you guys notice lack of interest/avaliable time in the courier suite (reading the last changelog, seems changes are more to complain with debian package policy that is innecesary respect real issues) ... and as far as I can see you are looking for the sources in sf instead of the right place which is the courier oficial download page, additional while the courier-mta sources are up to date in salsa-debian, the maildrop one in salsa-debian are too old respect the mta suite! while I made my own package on OBS vegnuli home for Devuan and Debian, is you guys need help i'm a often user of the complete suite and not just parts or toys of, maildrop can be build with two ways: * set GID mail without restricted caller (maildrop) * set UID root with restricted caller for courier-mta (maildrop-courier) -- missing and the way i set in my package cos is the need by the original suite the courier-mta NOTE: Courier maildrop in debian present a very not proper behaviour.. original sources are from courier and any other implementation are non-related and users can fork the software, cases like #375589 are not valid cos seems maildrop (as author make it for courier filtering) is a courier implementation if applies! so any external specific usage are purely optional This are related to #910380 (separate makemime from sources) #204187, #596057 & #375589#26 (bad usage cos is not made for), #481223 (changed behaviour cos is not made for, what?), #592585 (dovecot specific crap) and go and go.. seems people thinks that maildrop are made for others rather than the courier suite... funny please close all of those package cos seems many of them are not supported by upstream and community must make a fork in those several cases! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#716252: fixed upstream, please check
Package: maildrop Version: 2.9.3-2 Severity: important The maildrop package in debian is severely out of sync and outdated: First of all stop of "Upstream is not willing to add another feature", seems people dont understan maildrop are made for courier, This specific problem was fixed upstream, please check * rfc2045/reformime.c (main2): fix crash if -x or -X is specified without the corresponding -s option. related to #716252 Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#481223: new release urgent cos several out of sync and fixeds
Package: maildrop Version: 2.9.3-2 Severity: important The maildrop package in debian is severely out of sync and outdated: First of all stop of "Upstream is not willing to add another feature", seems people dont understan maildrop are made for courier, and if need can proposed a fork for that! Second: **several problems where aborted upstream**, the most important ones are: * libs/maildrop/deliver.C (delivery): Always return 75 upon delivery failure, for the standalone maildrop build. related to #481223 * libs/maildir/maildirmake.c (main): maildirmake's -q option will create the maildir if it does not exist. related to #501557 * libs/rfc2045/reformime.c (main2): Fix crash when the -s option is not valid. related to #71625 * rfc2045/reformime.c (main2): fix crash if -x or -X is specified without the corresponding -s option. related to #71625 A new maildrop pack is required and this must either come from the same courier sources (#867121) or update the one... this last seems quite stupid as courier is the official sources of maildrop and although it is offered separately by the author upstream, unifying it will improve maintenance from a team, and as you guys notice lack of interest/avaliable time in the courier suite (reading the last changelog, seems changes are more to complain with debian package policy that is innecesary respect real issues) ... and as far as I can see you are looking for the sources in sf instead of the right place which is the courier oficial download page, additional while the courier-mta sources are up to date in salsa-debian, the maildrop one in salsa-debian are too old respect the mta suite! while I made my own package on OBS vegnuli home for Devuan and Debian, is you guys need help i'm a often user of the complete suite and not just parts or toys of, maildrop can be build with two ways: * set GID mail without restricted caller (maildrop) * set UID root with restricted caller for courier-mta (maildrop-courier) -- missing and the way i set in my package cos is the need by the original suite the courier-mta NOTE: Courier maildrop in debian present a very not proper behaviour.. original sources are from courier and any other implementation are non-related and users can fork the software, cases like #375589 are not valid cos seems maildrop (as author make it for courier filtering) is a courier implementation if applies! so any external specific usage are purely optional This are related to #910380 (separate makemime from sources) #204187, #596057 & #375589#26 (bad usage cos is not made for), #481223 (changed behaviour cos is not made for, what?), #592585 (dovecot specific crap) and go and go.. seems people thinks that maildrop are made for others rather than the courier suite... funny please close all of those package cos seems many of them are not supported by upstream and community must make a fork in those several cases! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#867121: courier-maildrop removel crap
I have xpecting issues with the courier due this bug of maildrop.. cos we cannot follow courier upstream recommendations.. I ask about that upstream.. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#556448: Its not courier problem, at problem, please closed
hi confirmed this is not courier problem, at problem: i try all the commands and always courier delivers the mail .. (including the commands in #430166) 1. First of all, commands are wrong! cos sendmail provided by courier does not take "-i" or "-t" or "-s" parameters.. just ignored and all parameters that are not valid will be taken as addresses.. so in #430166 that's the reason of vanished mails 2. last mail here confirmed was an at problem bug so please close this bug ! issue was solved at at (3.1.12-1) Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#357769: courier-imap: suspected fam subscription leaks
Please close this issue: This is a memory issue.. solutiion is simple icrease ram usage by courier.. there's no more solution Also it has combined exim4 shit i already make some test with debian 6 and debian 9 (courier 0.6X and courier 1.0.6 respectivelly backported) and for huge amounts of mails (around of thousands of in courier-mlm) the solution was increase ram usage and daemons (config files pointing that) -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#974585: current patch only hides error but still happened
Package: courier-mta Version: 1.0.6-1 Severity: critical Justification: hide real errors as of 0015-Disable-imapscanfail-maildirwatch-error-reporting.patch only hide the error message and seems real solution are by install FAM please check https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578937#105 -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#599682:
PLEASE CLOSE THIS ISSUE and mark as resolved: this issue is not a duplicate of #578937 and the typo was merged with the patch discuss here: https://sourceforge.net/p/courier/mailman/courier-users/thread/4ba4f266.3080...@linuxia.de/ the issue #578937 [1] is now another different one! i mail in that property of course NOTE: also this threath has 3 spam mails 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578937 -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#946591: mkesmtpdcert does not make file where it said (seems solved)
Seems this issue is solved with the patch 0012-Define-and-use-PEMFILE-in-mkesmtpdcert.patch please confirm and close -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#933948: systemd forces stop and garbage in coureir again
i checked this in devuan (it lacks of systemd) and does work..but not on debian root@venenux:~# service courier-imap-ssl status ● courier-imap-ssl.service - LSB: Courier IMAP server (TLS) Loaded: loaded (/etc/init.d/courier-imap-ssl; generated) Active: active (exited) since Mon 2020-10-05 15:28:47 VET; 34s ago it said "active" but (exited) seems, premature received success of lauch .. i guess cos there's no such good control of pid file if process broke: based on https://sourceforge.net/p/courier/mailman/message/35056163/ seems systemd cannot handle that! maybe that's why by the sysv script does work! again systemd problem related Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#956414: +1 we need more away from systemd
+1 good work.. please core DD this pacakge need a review! in devuan works as expected -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#933734: CRTL+ARROWS switch but does not really now
tryit new version, this time let me redefine keys and works, but by default does not work! gtk2 works perfectly (debian wheeze with older version custon build) 2020-05-10 8:32 GMT-04:00, Andreas Ronnquist : > On Tue, 6 Aug 2019 08:30:10 -0400 PICCORO McKAY Lenz > wrote: >> i created manually the file.. now the config as you pointed was put.. >> >> BUT graphically seems change to the next terminal.. but the internal >> screeen still show the current terminal >> >> it's clear that the sakura release are totally broken but why? >> libvte? gtk3 ? >> > > I cannot reproduce your problem, it works just find over here. I have > uploaded a new version of sakura (3.7.1-1), could you please try this > version and check if you can reproduce the problem in this version? > > /Andreas > gus...@debian.org > -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#955603: those modules are STILL IN RECENT SERVERS like r128 (rage) and openchrome via boards
those modules are STILL IN RECENT SERVERS like r128 (rage) and openchrome via boards proliant hp and DELL ones! -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#955603: r128 has updates recently
https://www.phoronix.com/scan.php?page=news_item=ATI-RAGE-128-DDX-6.11.0 2020-04-26 23:32 GMT-04:00, PICCORO McKAY Lenz : > those modules are STILL IN RECENT SERVERS like r128 (rage) and > openchrome via boards > > proliant hp and DELL ones! > > -- > Lenz McKAY Gerardo (PICCORO) > http://qgqlochekone.blogspot.com > -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#844049: Bug#951593: cups-filters: Cups filters has hard depends on imagemagick makes unnistallable
El mié., 19 de feb. de 2020 a la(s) 12:56, Didier 'OdyX' Raboud (o...@debian.org) escribió: > > Hello Lenz, and thanks for taking the time to report this bug. only two persons can made it! but what happened if not? do you know that the report bug seems a bit complicateed for mayority of persons? i can understand that of course it's not a simle piece of a single software.. but.. this problem has several mounts happened and nobody takes the care! >This was fixed in 1.14.0-2; and is therefore already fixed in stable, testing > and unstable. It is arguably a bug (but not a grave one) in versions before > stable, but I (as maintainer) will not get it fixed in these ancient versions, > as that would clearly be a disruptive change, unacceptable for Debian > (old)stable versions. so stable has no import6ance? interesting.. we must use unstalbel due unstable are the target stable to bugfixeds, puff > > Le mercredi, 19 février 2020, 16.52:05 h CET PICCORO McKAY Lenz a écrit : > > please we must said hard words to make this some noise and take attention? > Threats of any kind are _not welcome_ in Debian; please reconsider the use of > this type of language. (Also, it doesn't _motivate_ me to help you, much the > contrary) seems in history of debian only noise cause changes.. see systemd problems! see etch migration.. see DEvuan migration? where goes the quality? > > -- > OdyX
Bug#844049: cups-filters: Cups filters has hard depends on imagemagick makes unnistallable
seems 844049 and 951593are also affected! please we must said hard words to make this some noise and take attention? cups-filters are the problem.. so then make something! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#951593: cups-filters: Cups filters has hard depends on imagemagick makes unnistallable
Package: cups-filters, Version: 2.2.1-8+deb9u4 Severity: grave Dear Maintainer, * What led up to the situation? try to install several times in several machines graphicmagicks event imagemagick (graphicsmagick-imagemagick-compat)m but it's impossible.. cups-filters package has a hard depends on imagemagick.. and this cupsfilters are required by lsb-printin and hp cups modules * What exactly did you do (or not do) that was effective (or ineffective)? apt-get install graphicsmagick-imagemagick-compat This len in that state: Following packages will be erased: ayatana-indicator-printers cups cups-filters cups-pdf hplip imagemagick imagemagick-6.q16 printer-driver-cups-pdf printer-driver-gutenprint printer-driver-hpcups printer-driver-pxljr printer-driver-splix task-print-server * What was the outcome of this action? uninstalable due removes my cups system as i have running perfectly, after command performs, cups hp printers does not work! * What outcome did you expect instead? alternate depends on cups-filters to be able to install graphicsmagick-imagemagick-compat -- System Information: Distributor ID: Debian Description: Debian GNU/Linux 9.10 (strecht) Release: 9.10 Codename: strecht Architecture: x86_64 Kernel: Linux 4.9.0-11-amd64 (SMP w/2 CPU cores) Locale: LANG=es_VE.UTF-8, LC_CTYPE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages cups-filters depends on: ii bc 1.06.95-9+b3 ii cups-filters-core-drivers1.11.6-3+deb9u1 ii ghostscript 9.26a~dfsg-0+deb9u6 ii imagemagick 8:6.9.7.4+dfsg-11+deb9u7 ii imagemagick-6.q16 [imagemagick] 8:6.9.7.4+dfsg-11+deb9u7 ii libc62.24-11+deb9u4 ii libcups2 2.2.1-8+deb9u4 ii libcupsfilters1 1.11.6-3+deb9u1 ii libcupsimage22.2.1-8+deb9u4 ii libfontconfig1 1:2.13.0-5 ii libfontembed11.11.6-3+deb9u1 ii libgcc1 1:6.3.0-18+deb9u1 ii libijs-0.35 0.35-12 ii libpoppler64 0.48.0-2+deb9u2 ii libqpdf176.0.0-2 ii libstdc++6 6.3.0-18+deb9u1 ii poppler-utils0.48.0-2+deb9u2 Versions of packages cups-filters recommends: ii liblouisutdml-bin 2.6.0-3+b2 Versions of packages cups-filters suggests: pn antiword pn docx2txt ii foomatic-db-compressed-ppds [foomatic-db] 20161201-1 -- no debconf information Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#950593: clonezilla, raises many errors when clone on the fly
Package: clonezilla Version: 3.27.16-1 Severity: normal seems problems are related to the new behaviour of the systemd and limited PATH's ... trying to clone on the fly partitions beetween disk give me errors before continue at confirm questions: /usr/sbin/ocs-onthefly: line 2247: ocs_onthefly_param_postaction_after_clone: command not found after clone more errors: *. /usr/sbin/ocs-onthefly: line 2545: /var/lib/clonezilla/ocs-vars: No such file or directory /usr/sbin/ocs-onthefly: line 2546: /var/lib/clonezilla/ocs-vars: No such file or directory /usr/sbin/ocs-onthefly: line 2547: /var/lib/clonezilla/ocs-vars: No such file or directory Checking if udevd rules have to be restored... Now syncing - flush filesystem buffers... Ending /usr/sbin/ocs-onthefly at 2020-02-03 22:17:57 UTC... -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (990, 'stable'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 4.13.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8), LANGUAGE=es_VE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages clonezilla depends on: ii bc 1.06.95-9+b3 ii dialog 1.3-20160828-2 ii drbl2.20.11-1 ii file1:5.30-1+deb9u1 ii gdisk 1.0.1-1 ii pigz2.3.4-1 ii util-linux 2.29.2-1 Versions of packages clonezilla recommends: pn partclone pn partimage Versions of packages clonezilla suggests: ii cifs-utils 2:6.7-1 ii openssh-client 1:7.6p1-2 pn sshfs pn udpcast -- no debconf information Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#950575: kamailio manual install fails die modules are not yet in path?¡
i tested in another vm instance too, AWS copied from the previous one, but clean before install kamailio: here are the requested info in clean environment: El lun., 3 de feb. de 2020 a la(s) 14:39, Michael Biebl (bi...@debian.org) escribió: > systemctl cat kamailio.service # /lib/systemd/system/kamailio.service [Install] WantedBy=multi-user.target [Unit] Description=Kamailio (OpenSER) - the Open Source SIP Server Documentation=man:kamailio(8) Wants=network-online.target After=network-online.target [Service] Type=forking User=kamailio Group=kamailio Environment='CFGFILE=/etc/kamailio/kamailio.cfg' Environment='SHM_MEMORY=112' Environment='PKG_MEMORY=18' EnvironmentFile=-/etc/default/kamailio EnvironmentFile=-/etc/default/kamailio.d/* # PIDFile requires a full absolute path PIDFile=/run/kamailio/kamailio.pid # ExecStart requires a full absolute path ExecStart=/usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY Restart=on-failure # /run/kamailio in tmpfs RuntimeDirectory=kamailio RuntimeDirectoryMode=0750 > systemctl status kamailio.service ● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/lib/systemd/system/kamailio.service; enabled) Active: active (running) since Mon 2020-02-03 18:59:08 UTC; 10min ago Docs: man:kamailio(8) Process: 21724 ExecStart=/usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY (code=exited, status=0/SUCCESS) Main PID: 21726 (kamailio) CGroup: /system.slice/kamailio.service ├─21726 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21727 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21728 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21729 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21730 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21731 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21732 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21733 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21734 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21735 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21736 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21737 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21738 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21739 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21740 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21741 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21742 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21743 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21744 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21745 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21746 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21747 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21748 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21749 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21750 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21751 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21752 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21753 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21754 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21755 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 └─21756 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12
Bug#950575: kamailio manual install fails die modules are not yet in path?¡
> Please run > reportbug --template systemd > reportbug --template kamailio already done, i already provide my 5c so ..for next pieces of info requested, i must to reinstall again all the image, as i described, if i install alone kamailio starts, but if i installed with some others modules does not start intil rest of packages are installed, this it's my las mail due i'm also busy and i provide my 5c > systemctl cat kamailio.service # /lib/systemd/system/kamailio.service [Install] WantedBy=multi-user.target [Unit] Description=Kamailio (OpenSER) - the Open Source SIP Server Documentation=man:kamailio(8) Wants=network-online.target After=network-online.target [Service] Type=forking User=kamailio Group=kamailio Environment='CFGFILE=/etc/kamailio/kamailio.cfg' Environment='SHM_MEMORY=64' Environment='PKG_MEMORY=8' EnvironmentFile=-/etc/default/kamailio EnvironmentFile=-/etc/default/kamailio.d/* # PIDFile requires a full absolute path PIDFile=/run/kamailio/kamailio.pid # ExecStart requires a full absolute path ExecStart=/usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY Restart=on-failure # /run/kamailio in tmpfs RuntimeDirectory=kamailio RuntimeDirectoryMode=0770 > systemctl status kamailio.service ● kamailio.service - Kamailio (OpenSER) - the Open Source SIP Server Loaded: loaded (/lib/systemd/system/kamailio.service; enabled) Active: active (running) since Mon 2020-02-03 18:52:06 UTC; 2s ago Docs: man:kamailio(8) Process: 21724 ExecStart=/usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f $CFGFILE -m $SHM_MEMORY -M $PKG_MEMORY (code=exited, status=0/SUCCESS) Main PID: 21726 (kamailio) CGroup: /system.slice/kamailio.service ├─21726 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21727 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21728 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21729 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21730 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21731 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21732 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21733 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21734 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21735 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21736 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21737 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21738 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21739 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21740 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21741 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21742 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21743 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21744 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21745 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21746 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21747 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21748 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21749 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21750 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21751 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21752 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21753 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21754 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.cfg -m 112 -M 12 ├─21755 /usr/sbin/kamailio -P /run/kamailio/kamailio.pid
Bug#950575: kamailio manual install fails die modules are not yet in path?¡
Package: kamailio,systemd Version: kamailio/5.3.0-1 Version: systemd/230-7 Severity: grave Another systemd related problem, (like happened with #921015 ), this error seems does not hapened if are installed with apt.get i try to install kamailio due other ways, like aptitude or gui others, and in those ways will fail, because first selected package to install are kamailio per se and some modules are not yet ready to use it, this is the output due the systemd "thing" .. does not happened in devuan with sysvinit or openrc only: Feb 3 17:25:58 10-101-2-99 systemd[1]: Starting Kamailio (Openser) SIP Server... Feb 3 17:25:58 10-101-2-99 systemd[21293]: Failed at step RUNTIME_DIRECTORY spawning /usr/sbin/kamailio: File exists Feb 3 17:25:58 10-101-2-99 systemd[1]: kamailio.service: control process exited, code=exited status=233 Feb 3 17:25:58 10-101-2-99 systemd[1]: Failed to start Kamailio (Openser) SIP Server. Feb 3 17:25:58 10-101-2-99 systemd[1]: Unit kamailio.service entered failed state. Feb 3 17:25:59 10-101-2-99 systemd[1]: kamailio.service holdoff time over, scheduling restart. Feb 3 17:25:59 10-101-2-99 systemd[1]: Stopping Kamailio (Openser) SIP Server... Feb 3 17:25:59 10-101-2-99 systemd[1]: Starting Kamailio (Openser) SIP Server... Feb 3 17:25:59 10-101-2-99 systemd[1]: Reloading. Feb 3 17:25:59 10-101-2-99 kamailio[21315]: loading modules under config path: /usr/lib/x86_64-linux-gnu/kamailio/modules/ Feb 3 17:25:59 10-101-2-99 kamailio[21315]: Listening on i cannot find what means "RUNTIME DIRECTORY" maybe are due in buster now path are not set and maybe does not find property the paths, but only happened with systemd related, i tested same package in devuan (yes, it works, taking directly from debian) and installs property.. i also tested with mxlinux and works too also.. Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#931862: O: citadel
i'm interesting in packaged and mantain citadel, have my own packages... i used citadel and noted the debian package are currently not working (does not created the socket) Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#946591: mkesmtpdcert does not make file where it said
Package: courier-mta Version: 1.0.6-1 Severity: critical Justification: causes serious data loss the mkesmtpdcert pgrogram in debian was altered, BUT are not in sync around documentations.. that may cause confusion and data loss due admins does not find resulting cert file and daemons does not start never: root@mail:/etc/courier# man mkesmtpdcert | grep pem /usr/lib/courier/esmtpd.pem. The mkesmtpdcert generates a self-signed X.509 certificate, mainly for testing. /usr/lib/courier/esmtpd.pem must be owned by the courier user and have no group or world permissions. The /usr/lib/courier/esmtpd.pem already exists. root@mail:/etc/courier# mkesmtpdcert /etc/courier/esmtpd.pem already exists. root@mail:/etc/courier# Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#805504: Citadel hangs after install so cannot continue..
The Citadel server hangs directly after it is started, so that Webcit and the comman-line client cannot connect: all the package was re-buiild agains sid and does not work.. i noted the bug 939377 and 943531 and 805504 seems happened with only debian packages and are related similar (or maybe same ) bugs i'll try a new upstream source directly from upstream and isntall in upstream way and report feedback Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#944610: breaking and inconsistent package configuration
Package: prosody Version: 0.11.3-1 Severity: important The configuration file /etc/prosody/prosody.cfg.lua should contain only global settings. Per-host configuration files should be placed in /etc/prosody/conf.avail/, and the active ones should be linked in /etc/prosody/conf.d/ but does not provide right instructions.. neither upstream has related! wiki Debian does not provide neither! stupid problems? i thinks so! are important problems Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#862300: continuos segfaults debian due systemd paths
since debian 10 path are not in root accoutn and then citadel does not work... citadel server also other must run several other commands and does not found those Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#943531: citadel does not creates socket unix and segfault at startup
Package: citadel-server Version: 917-2+b1 Severity: important Dear Maintainer, * What led up to the situation? installed citadel-suite and does not work since buster, systemd (again) startud does nto really start the service.. * What exactly did you do (or not do) that was effective (or ineffective)? only install citadel * What was the outcome of this action? does not stat, it said segfault and does not create socket. but daemon are running in fisrt place.. the isntallation scripts does not work due the new behaviour of systemd su command and forces me to use sudo.. but agains now start but does not creates socket.. also package creates a user and does not use to start the daemon.. * What outcome did you expect instead? it that question necesary? -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages citadel-server depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii libcitadel4917-2 ii libcurl4 7.64.0-4 ii libdb5.3 5.3.28+dfsg1-0.5 ii libexpat1 2.2.6-2 ii libical3 3.0.4-3 ii libldap-2.4-2 2.4.47+dfsg-3 ii libpam0g 1.3.1-5 ii libsieve2-12.2.6-2 ii libssl1.1 1.1.1c-1 ii lsb-base 10.2019051400 ii openssl1.1.1c-1 ii patch 2.7.6-3+deb10u1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages citadel-server recommends: pn db4.6-util ii shared-mime-info 1.10-1 citadel-server suggests no packages. -- Configuration Files: /etc/citadel/public_clients changed [not included] /etc/init.d/citadel changed [not included] -- debconf information: * citadel/Password: (password omitted) * citadel/Password_again: (password omitted) citadel/BadUser: citadel/LDAPBaseDN: dc=example,dc=com citadel/LDAPBindDN: * citadel/ServerIPAddress: 0.0.0.0 citadel/LDAPServer: 0.0.0.0 * citadel/LoginType: Internal citadel/LDAPBindDNPassword: OpenSesame * citadel/Administrator: citaroot citadel/LDAPServerPort: 389 Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#941740: /usr/sbin/dpkg-reconfigure: breaks reconfigure locales since systemd changes
Package: debconf Version: 1.5.38 Severity: important File: /usr/sbin/dpkg-reconfigure User: debian-d...@lists.debian.org Usin minimal net.install with no recommends breaks many packages setups: by example for locales: /var/lib/dpkg/info/locales.postinst: 64: /var/lib/dpkg/info/locales.postinst: locale-gen: not found Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#939406: UNGOOGLED-CHROMIUM EVENT CHROMIUM
Source: chromium-browser Severity: important Tags: patch I REVISED THE CHROMIUM AND CHROME AND SEEMS DOES NTO RESPECT THE FREEDOM OF THE USERS IN ANY CHANCE AFTER A REVIEW OVER THE UNGOOGLED CHROMIUM PROJECT.. https://github.com/ungoogled-software/ungoogled-chromium-debian As LXDE does in the past and today.. it's better that upstream work hand to hand with the debian itselft.. that's reduced the problems of updating things.. in chromium that are a very oftyen updated package... Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#933734: CRTL+ARROWS switch but does not really now
i created manually the file.. now the config as you pointed was put.. BUT graphically seems change to the next terminal.. but the internal screeen still show the current terminal it's clear that the sakura release are totally broken but why? libvte? gtk3 ? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#933734: ALT+LEFT or ALT+RIGHT arrow does not work anymore
so then "rm ~/.config/sakura/sakura.conf " then logout and login and start sakura.. then does not work seems the file are not readable due are not created when sakura starts!?? Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com El vie., 2 de ago. de 2019 a la(s) 19:55, Andreas Ronnquist ( gus...@debian.org) escribió: > What does your ~/.config/sakura/sakura.conf look like? > > I have > > switch_tab_accelerator=8 > > and > > prev_tab_key=Left > next_tab_key=Right > > in it, with the results that I can switch between the tabs using > Alt+Left and Alt+Right. > > What are the values of those settings in your sakura config file? > > /Andreas > gus...@debian.org >
Bug#933734: ALT+LEFT or ALT+RIGHT arrow does not work anymore
Package: sakura Version: 3.6.0-3 Severity: serious Justification: package application are not usable as released! in the manpage of the sakura it said that ALT+LEFT arrow change the terminal to the left nex and so same for right nex with right arrow.. since debian 10 this stop to work! that's all! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#933213: upgrades causes problems due newer openssl 102 vs 1.1.1
Package: courier-mta-ssl Version: 0.73.1-1.6 i upgrade from jessie to buster.. when pass to strech got a problem.. i must manually downgrade the openssl to jessie version before upgrade both openssl and courier, minimal version posible 1.0.2 before use the 1.1.1 or more up! Setting up courier-mta-ssl (0.73.1-1.6) ... Can't load /usr/lib/courier/esmtpd.rand into RNG 139827721225984:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:98:Filename=/usr/lib/courier/esmtpd.rand Generating a RSA private key writing new private key to '/tmp/tmp.ABP95tkPaE/esmtpd.pem' - Invalid command 'gendh'; type "help" for a list. dpkg: error processing package courier-mta-ssl (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for systemd (215-17+deb8u13) ... Errors were encountered while processing: courier-mta-ssl E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Setting up courier-mta-ssl (0.73.1-1.6) ... Generating a RSA private key .. .. writing new private key to '/tmp/tmp.jGwSHG2y5y/esmtpd.pem' - Invalid command 'gendh'; type "help" for a list. dpkg: error processing package courier-mta-ssl (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: courier-mta-ssl -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#863046: crash in menu->client
it's a problem in libjsoncpp library please archive the issue but marked that any other changes in libjsoncpp can again produce same error: https://bugs.debian.org/733974 i if dessire can be archived, but i thing (due debvian does not use the build in jsoncpp of minetest sources) must be take in more carefully i made packages for those people that need solution over current instllation THAT CANNOT BE UPGRADE DUE HARDWARE ARE NOT SUPPORTED BY NEWER KERNEL, also due Debian are too bussines-protocol complicated (several years later i must find the bug mby myselft event play the game) current: ttps://build.opensuse.org/project/show/home:vegnuli:minetest in future i'll move it to https://build.opensuse.org/project/show/home:vegnuli:games Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#832980: related openbox and obsession are not in sync
i have a package tha can be in a SR can anybody give a try?: https://build.opensuse.org/package/show/home:vegnuli:desktops/obsession Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com El jue., 6 de jun. de 2019 a la(s) 14:14, Fabien Givors ( f+deb...@chezlefab.net) escribió: > Le 02/06/2019 à 20:58, PICCORO McKAY Lenz a écrit : > > package openbox (3.6.1-8) unstable; tries to fix and close the bug > > #888254 but was incorrectly closed.. > > > > tested and try to set OnlyShowIn=Openbox; of OnlyShowIn=OPENBOX; does > > not work due the vars environment are not set in nowhere.. > > > > why the Debian need so many burocratic things to property fix the things? > > I currently don't have time to fix obsession (plus I don't have upload > rights). NMU are welcome. >
Bug#832980: related openbox and obsession are not in sync
i have a package that can be sponsored.. dsc file here, anyone can give a try ? http://download.opensuse.org/repositories/home:/vegnuli:/desktops/Debian_9.0/obsession_20140608-3.20180613.1.dsc El jue., 6 de jun. de 2019 a la(s) 14:14, Fabien Givors ( f+deb...@chezlefab.net) escribió: > Le 02/06/2019 à 20:58, PICCORO McKAY Lenz a écrit : > > package openbox (3.6.1-8) unstable; tries to fix and close the bug > > #888254 but was incorrectly closed.. > > > > tested and try to set OnlyShowIn=Openbox; of OnlyShowIn=OPENBOX; does > > not work due the vars environment are not set in nowhere.. > > > > why the Debian need so many burocratic things to property fix the things? > > I currently don't have time to fix obsession (plus I don't have upload > rights). NMU are welcome. >
Bug#832980: related openbox and obsession are not in sync
package openbox (3.6.1-8) unstable; tries to fix and close the bug #888254 but was incorrectly closed.. tested and try to set OnlyShowIn=Openbox; of OnlyShowIn=OPENBOX; does not work due the vars environment are not set in nowhere.. why the Debian need so many burocratic things to property fix the things? -- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#929383: live-build fails if there's some updates for same kernel
El mié., 22 de may. de 2019 a la(s) 11:30, PICCORO McKAY Lenz (
mckaygerh...@gmail.com) escribió:
>
> so then at the bvinary stage i got that error:
>
> mv: target ‘binary/live/vmlinuz1’ is not a directory
> P: Begin unmounting filesystems...
> P: Saving caches...
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> }
>
i got some point int the problem seem at scritps/build/binary_syslinux
commands seems are:
mv binary/${_INITRAMFS}/vmlinuz-*-${_FLAVOUR}
binary/${_INITRAMFS}/vmlinuz${_NUMBER}
this when executing for varous flavours with different verions got into
problems due made more than one file and obviousli rest of scripts got
confused
there's others scripts in same way fails if more than one are specified, by
example
and backports repository and updates repositories are enabled:
--security true backports true updates true \
--linux-flavours "586 686-pae amd64" \
--linux-packages "linux-image linux-headers" \
will fails
Bug#929383: live-build fails if there's some updates for same kernel
Package: live-build
Version: 1:20170213
Severity: serius
when try to build live strecht image with differents mirros (i setup not
only "mirror-" also setup "parent-mirror-" due bandwicht usage behind
firewallin also optimization of my bandwicht account spend..
IN ANY CASE: noted that i have various versions of the linux-image packages
(some from security others from recent uploads) such:
linux-image-4.9.0-9-686_4.9.168-1+deb9u2_i386.deb
linux-image-4.9.0-9-686_4.9.168-1_i386.deb
this happened if i configured http://ftp.wa.au.debian.org/debian as mirror
for live-build
so then at the bvinary stage i got that error:
mv: target ‘binary/live/vmlinuz1’ is not a directory
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists... Done
Building dependency tree
Reading state information... Done
NOTED THE "‘binary/live/vmlinuz1’ that i guess must be
‘binary/live/vmlinuz’ ?
i tried various configurations but the only working if when i disable all
mirrors configurations and only use only one mirror for all the stages...
and if those mirrors are only in sync...
i think the mirror "out of sync" are not a response to the problem due the
scripts must only take the configured version that i suppot to point at the
command line such :
--linux-flavours "586 686-pae" \
--linux-packages "linux-image linux-headers" \
This does not happened with amd64 if i build jessie image but fails for all
setup of i386 using any release such stretch, buster of oldstable when te
mirrors are not in sync with most recents
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Description: rollback the drop of the backports customizations due now merged in main repo
Author: PICCORO Lenz McKAY
---
Origin: https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2
--- live-build-4.0.4.orig/functions/defaults.sh
+++ live-build-4.0.4/functions/defaults.sh
@@ -435,6 +435,31 @@ Set_defaults ()
;;
esac
+ # Setting backports mirror to fetch packages from
+ case "${LB_MODE}" in
+ debian)
+ _DISTRIBUTOR="$(lsb_release -sc)"
+ case "${_DISTRIBUTOR}" in
+jessie|wheeze)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-http://archive.debian.org/debian-backports/};
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT_BACKPORTS}}"
+ ;;
+*)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-http://backports.debian.org/debian-backports/};
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT_BACKPORTS}}"
+ ;;
+ esac
+ ;;
+
+ progress-linux)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT}}"
+ ;;
+ *)
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-none}"
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-none}"
+ ;;
+ esac
+
# Setting mirror which ends up in the image
case "${LB_MODE}" in
debian)
@@ -489,6 +514,30 @@ Set_defaults ()
;;
esac
+ # Setting backports mirror which ends up in the image
+ case "${LB_MODE}" in
+ debian)
+ _DISTRIBUTOR="$(lsb_release -sc)"
+ case "${_DISTRIBUTOR}" in
+jessie|wheeze)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-http://archive.debian.org/debian-backports/};
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT_BACKPORTS}}"
+ ;;
+*)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-http://ftp.de.debian.org/debian-backports/};
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT_BACKPORTS}}"
+ ;;
+ esac
+ ;;
+ progress-linux)
+ LB_MIRROR_BINARY_BACKPORTS="${LB_MIRROR_BINARY_BACKPORTS:-${LB_MIRROR_BINARY}}"
+ ;;
+ *)
+ LB_PARENT_MIRROR_BINARY_BACKPORTS="${LB_PARENT_MIRROR_BINARY_BACKPORTS:-none}"
+ LB_MIRROR_BINARY_BACKPORTS="${LB_MIRROR_BINARY_BACKPORTS:-none}"
+ ;;
+ esac
+
case "${LB_MODE}" in
progress-linux)
LB_PARENT_MIRROR_DEBIAN_INSTALLER="${LB_PARENT_MIRROR_DEBIAN_INSTALLER:-${LB_MIRROR_CHROOT}}"
--- live-build-4.0.4.orig/scripts/build/chroot_archives
+++ live-build-4.0.4/scripts/build/chroot_archives
@@ -160,11 +160,11 @@ EOF
debian)
if [ "${LB_PARENT_DISTRIBUTION}" != "sid" ]
then
- echo "deb ${LB_PARENT_MIRROR_CHROOT} ${LB_PARENT_DISTRIBUTION}-backports ${LIVE_IMAGE_PARENT_ARCHIVE_AREAS}" >> chroot/etc/apt/${_PARENT_FILE}
+ echo "deb ${LB_PARENT_MIRROR_CHROOT_BACKPORTS} ${LB_PARENT_DISTRIBUTION}-backports ${LIVE_IMAGE_PARENT_ARCHIVE_AREAS}" >> chroot/etc/apt/${_PARENT_FILE}
if [ "${_PASS}" = "source" ] || [ "${LB_APT_SOURCE_ARCHIVES}" = "true" ]
then
- echo "deb-src ${LB_PARENT_MIRROR_CHROOT} ${LB_PARENT_DISTRIBUTION}-backports ${LIVE_IMAGE_PARENT_ARCHIVE_AREAS}" >> chroot/etc/apt/${_PARENT_FILE}
+ echo "deb-src ${LB_PARENT_MIRROR_CHROOT_BACKPORTS} ${LB_PARENT_DISTRIBUTION}-backports
Bug#929271: backports customizations are not enabled for live-build
A SPECIAL NOTE ABOUT THIS: El mié., 22 de may. de 2019 a la(s) 06:18, Roland Clobus (rclo...@rclobus.nl) escribió: > Issue 2: Building a live image for jessie > Jessie is now oldstable, and will soon (TM) be oldoldstable. Unless you > have a compelling reason to use jessie, I would suggest to pick stretch > or perhaps even buster. NONE OF THOSE WILL WORK WITH MY CAPTURE CARDS FRAMEGRABBER (that the driver was removed somehwere in 4.X) NONE OF THOSE NOW WORK IN MY Pentium II 550MHZ used to play NES and DOS games NONE OF THOSE NOW WORK "enoucht decent" in my older machiens and i have a lot of thems before you says "buy newer" i remenber here that not all the countries have lot of money to buy machines so easyle! > > Note: lb config --distribution stretch works fine > Note: lb config --distribution buster works fine too > > Issue 3: Unrecognized command line option > > As noted in my first response to this bug report, I will update the > manual to match the current code. The time I spent on writing this mail > has provided me with lots of information on how to update the manual to > match the current implementation of the live-image building tools. > > Issue 4: the program gives options to alter all sources of packages > except the "backports" > > > [snip] the > > program gives options to alter all sources of packages except the > > "backports"... because you can alter all and not that? > > I think I answered this question with the test for backports as > mentioned with issue 1. Support for backports is not in the basic > configuration of 'lb config', you need to explicitly add support for > that repository, and you can use the configuration files for that. > > > I don't think that the excuse of "all are always in the same source" is > > valid, because according to the installation images as well as the > > backports images are not always coordinated between all the mirrors > > origins according to the debian notes. > > I am not aware of these notes, on which URL can I find them? > It can be that local mirror will not be synced yet or only a partial > mirror, but you can always add an additional repository. > > > In addition, not all the countries have excelent internet providers and > > the net service are expensive in some cases.. > > For that, you can use something like apt-cacher-ng during the > construction of the live image. > > Summmary: from my personal point of view, only issue 3 remains. > > With kind regards, > Roland Clobus > > [1] https://lists.debian.org/debian-devel-announce/2019/03/msg6.html > [2] https://backports.debian.org/Instructions/ > [3] https://wiki.debian.org/DebianGeoMirror > [4] > https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2 > [5] > https://salsa.debian.org/live-team/live-build/commit/68700f466c142082e7423282ca4caaf7552bf8e9 > [6] > https://live-team.pages.debian.net/live-manual/html/live-manual/customizing-package-installation.en.html#379 > [7] http://ftp.debian.org/debian/dists/jessie-updates/ >
Bug#929364: live-manual out of sync with lasted bug#929271 and live-build changes
Package: live-manual Hi i separate this issue from bug #929271 where we pointing some misconfigurations and references out of date, including links of documentation El mié., 22 de may. de 2019 a la(s) 06:18, Roland Clobus (rclo...@rclobus.nl) escribió: > > Issue 3: Unrecognized command line option > > As noted in my first response to this bug report, I will update the > manual to match the current code. The time I spent on writing this mail > has provided me with lots of information on how to update the manual to > match the current implementation of the live-image building tools. i revised the live manual and there's too many work to do.. i can help and to get sure this are in good made i opened this bug report and please do not close until we can check that all need references are corrected.. in any case if think it's not necesary please close as soon as possible i just now building images with live-build of jessie, strecht and buster so i can check in mayor way if the results are enought > > I am not aware of these notes, on which URL can I find them? > It can be that local mirror will not be synced yet or only a partial > mirror, but you can always add an additional repository. >
Bug#929271: backports customizations are not enabled for live-build
Hi Roland.. let's forget the jessie related.. ok answering your mail: El mié., 22 de may. de 2019 a la(s) 06:18, Roland Clobus (rclo...@rclobus.nl) escribió: > The title says: backports customizations are not enabled for live-build > yeah! > The content says: Unrecognized command line option > osposweb replied with: the program gives options to alter all sources of > packages except the "backports" > same here! so i think it's same issue > Issue 1: backports customizations are not enabled for live-build > > Regarding the Debian mirrors: as I understand, Debian nowadays has > reduced the configuration for finding the mirrors, by using > deb.debian.org for all current releases, architectures and geographical > locations. The backports for stretch are there [2], and all geographical > locations can use the same URL [3]. > Yes, forgetting about jessie which play off soon .. affects future compilations of live build > However, if you need to add other repositories, the manual at section > 8.1.5 [6] states that you need to add specific files: > config/archives/your-repository.list.chroot and/or > config/archives/your-repository.list.binary. Within these files you can > write lines with the same syntax as you would do in /etc/apt/sources.list. > THIS WORK ONLY FOR CHROOT! must work for all the stages! > (Note that I still have not touched chapter 8 of the manual, there are > still some old references to alioth.debian.org.) > So for getting access to other repositories, you should use these files, > and not one of the command line options. > About older references, i can open a new bug reports for.. but for now, this issue are only related to allow to customize backports mirrors > I have tested backports with: > lb config --distribution stretch > echo "deb http://deb.debian.org/debian stretch-backports main" > > config/archives/live.list.chroot > echo "deb http://deb.debian.org/debian stretch-backports main" > > config/archives/live.list.binary > The backports are available, but grep is still at 2.27-2 instead of > 3.3-1~bpo9+1. So I did not correctly configure apt pinning. > BAD MADE the pinning works but in some stages does not sync with chroot installed In any case, i want to use different mirrors for backports due bandwith usage behind firewalling Issue 2: Building a live image for jessie > Well in this case i there's too much work forgett, due as i exposed: i want to use different mirrors for backports due bandwith usage behind firewalling for live-strecht and future live builds Issue 3: Unrecognized command line option > > Summmary: from my personal point of view, only issue 3 remains. > all of the documentations are out of wync that resumes the "unrecognized..." > > With kind regards, > Roland Clobus > > [1] https://lists.debian.org/debian-devel-announce/2019/03/msg6.html > [2] https://backports.debian.org/Instructions/ > [3] https://wiki.debian.org/DebianGeoMirror > [4] > > https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2 > [5] > > https://salsa.debian.org/live-team/live-build/commit/68700f466c142082e7423282ca4caaf7552bf8e9 > [6] > > https://live-team.pages.debian.net/live-manual/html/live-manual/customizing-package-installation.en.html#379 > [7] http://ftp.debian.org/debian/dists/jessie-updates/ > >
Bug#929271: backports customizations are not enabled for live-build
obviously you Maichael do not paid attention, i repeat: 1. the bug was reported agains strecht.. i cannot build strecht image using different mirrors for each case! 2. -for low performance networks it's a good practice have differents mirrors so download task will be separatelly, 3. docummentation are obviuslly out of date, script obvouslly are out of date, all are obviouslly out of sync in any case, that are ilogic, iu can provide different mirror for chroot installer and for booststrap but not for backports? PUFFF i mean event have normal and backports in same domain.. i setup different origin domains sources for normal repository and backports repository... that's a good practice Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com El mar., 21 de may. de 2019 a la(s) 15:16, Michael . (keltoi...@gmail.com) escribió: > Jessie security support ended June 17 2018. Asking the live project to > support a dist that is no longer security supported adds work to an > already huge workload. > > On 22/05/2019, PICCORO McKAY Lenz wrote: > > Roland, i track back all the history and get not lost.. BUT IN ANY CASE > > THAT BEHAVIOUR ARE NOT VIABLE, lest see: > > > > about the commits history: seems the migration was not as espected > > (migrations was done good but the results are not same as xpected) > > > > the commits are : > > > https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2 > > > > and also > > > https://salsa.debian.org/live-team/live-build/commit/68700f466c142082e7423282ca4caaf7552bf8e9 > > > > I EXPLAIN WHY THAT COMMITS MUST BE REVERTED > > > > 1. - the mirror are track from default mirror.. so oldstable moving of > > backports (as seems always) are not in same repository, that made this > > behaviour ilogic and ridiculus, due for olstable the repository will be > > archived .. same for updates repository! > > > > 2. -for low performance networks it's a good practice have differents > > mirrors so download task will be separatelly, i mean event have normal > and > > backports in same domain.. i setup different origin domains sources for > > normal repository and backports repository... that's a good practice > > > > there's more reason but in my case those are enouoght > > > > Please therat that issue quick due i cannot build any jessie image > property > > or i cannot use any strecth image in good shape! > > > > Lenz McKAY Gerardo (PICCORO) > > http://qgqlochekone.blogspot.com > > > > > > El mar., 21 de may. de 2019 a la(s) 02:38, Roland Clobus > > (rclo...@rclobus.nl) > > escribió: > > > >> Hello PICCORO, > >> > >> On 20/05/2019 15:42, PICCORO McKAY Lenz wrote: > >> > when try to build live jessie image using strecht i got those errors > >> > > >> > lb config: unrecognized option '--mirror-chroot-updates' > >> > lb config: unrecognized option '--parent-mirror-binary-updates' > >> > lb config: unrecognized option '--parent-mirror-chroot-updates' > >> > >> When working on the documentation, I've noticed these command line > >> options as well. They are not present in the scripts, they are only in > >> the documentation. > >> Unfortunately due to the migration from alioth to salsa the git history > >> got lost, so I cannot trace it back. I would assume that the > >> functionality was remove from the scripts at some time, and that someone > >> forgot to update the documentation accordingly. I've downloaded the > >> package 1:20151215 [1], and the command line is mentioned there also > >> only in the documentation, which confirms my assumption. > >> > >> Instead of (re-)implementing these options, I would update the > >> documentation instead. > >> > >> With kind regards, > >> Roland Clobus > >> > >> [1] https://snapshot.debian.org/package/live-build/1%3A20151215/ > >> > >> > >> > >> > > >
Bug#929271: backports customizations are not enabled for live-build
Roland, i track back all the history and get not lost.. BUT IN ANY CASE THAT BEHAVIOUR ARE NOT VIABLE, lest see: about the commits history: seems the migration was not as espected (migrations was done good but the results are not same as xpected) the commits are : https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2 and also https://salsa.debian.org/live-team/live-build/commit/68700f466c142082e7423282ca4caaf7552bf8e9 I EXPLAIN WHY THAT COMMITS MUST BE REVERTED 1. - the mirror are track from default mirror.. so oldstable moving of backports (as seems always) are not in same repository, that made this behaviour ilogic and ridiculus, due for olstable the repository will be archived .. same for updates repository! 2. -for low performance networks it's a good practice have differents mirrors so download task will be separatelly, i mean event have normal and backports in same domain.. i setup different origin domains sources for normal repository and backports repository... that's a good practice there's more reason but in my case those are enouoght Please therat that issue quick due i cannot build any jessie image property or i cannot use any strecth image in good shape! Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com El mar., 21 de may. de 2019 a la(s) 02:38, Roland Clobus (rclo...@rclobus.nl) escribió: > Hello PICCORO, > > On 20/05/2019 15:42, PICCORO McKAY Lenz wrote: > > when try to build live jessie image using strecht i got those errors > > > > lb config: unrecognized option '--mirror-chroot-updates' > > lb config: unrecognized option '--parent-mirror-binary-updates' > > lb config: unrecognized option '--parent-mirror-chroot-updates' > > When working on the documentation, I've noticed these command line > options as well. They are not present in the scripts, they are only in > the documentation. > Unfortunately due to the migration from alioth to salsa the git history > got lost, so I cannot trace it back. I would assume that the > functionality was remove from the scripts at some time, and that someone > forgot to update the documentation accordingly. I've downloaded the > package 1:20151215 [1], and the command line is mentioned there also > only in the documentation, which confirms my assumption. > > Instead of (re-)implementing these options, I would update the > documentation instead. > > With kind regards, > Roland Clobus > > [1] https://snapshot.debian.org/package/live-build/1%3A20151215/ > > > >
Bug#832682: still have destroyect behing customized network and firewall
similar but not equal scenario happened to me and i must enabled internal mirrors repositories that also faild due bug #929271 Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
Bug#929271: backports customizations are not enabled for live-build
Package: live-build
Version: 1:20170213
Severity: important
Tags: patch
when try to build live jessie image using strecht i got those errors
lb config: unrecognized option '--mirror-chroot-updates'
lb config: unrecognized option '--parent-mirror-binary-updates'
lb config: unrecognized option '--parent-mirror-chroot-updates'
i bypass these options due main debian repositories have not jessie backports..
in any case.. when try to build any live flavor.. it failds and the
option are documented.
the attached patch i provides could solve if ...
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Description: rollback the drop of the backports customizations due now merged in main repo
Author: PICCORO Lenz McKAY
---
Origin: https://salsa.debian.org/live-team/live-build/commit/dd15ade8bbdc6360816ed858253e7aaa68e4c9c2
--- live-build-4.0.4.orig/functions/defaults.sh
+++ live-build-4.0.4/functions/defaults.sh
@@ -435,6 +435,31 @@ Set_defaults ()
;;
esac
+ # Setting backports mirror to fetch packages from
+ case "${LB_MODE}" in
+ debian)
+ _DISTRIBUTOR="$(lsb_release -sc)"
+ case "${_DISTRIBUTOR}" in
+jessie|wheeze)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-http://archive.debian.org/debian-backports/};
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT_BACKPORTS}}"
+ ;;
+*)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-http://backports.debian.org/debian-backports/};
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT_BACKPORTS}}"
+ ;;
+ esac
+ ;;
+
+ progress-linux)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT}}"
+ ;;
+ *)
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-none}"
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-none}"
+ ;;
+ esac
+
# Setting mirror which ends up in the image
case "${LB_MODE}" in
debian)
@@ -489,6 +514,30 @@ Set_defaults ()
;;
esac
+ # Setting backports mirror which ends up in the image
+ case "${LB_MODE}" in
+ debian)
+ _DISTRIBUTOR="$(lsb_release -sc)"
+ case "${_DISTRIBUTOR}" in
+jessie|wheeze)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-http://archive.debian.org/debian-backports/};
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT_BACKPORTS}}"
+ ;;
+*)
+ LB_MIRROR_CHROOT_BACKPORTS="${LB_MIRROR_CHROOT_BACKPORTS:-http://ftp.de.debian.org/debian-backports/};
+ LB_PARENT_MIRROR_CHROOT_BACKPORTS="${LB_PARENT_MIRROR_CHROOT_BACKPORTS:-${LB_MIRROR_CHROOT_BACKPORTS}}"
+ ;;
+ esac
+ ;;
+ progress-linux)
+ LB_MIRROR_BINARY_BACKPORTS="${LB_MIRROR_BINARY_BACKPORTS:-${LB_MIRROR_BINARY}}"
+ ;;
+ *)
+ LB_PARENT_MIRROR_BINARY_BACKPORTS="${LB_PARENT_MIRROR_BINARY_BACKPORTS:-none}"
+ LB_MIRROR_BINARY_BACKPORTS="${LB_MIRROR_BINARY_BACKPORTS:-none}"
+ ;;
+ esac
+
case "${LB_MODE}" in
progress-linux)
LB_PARENT_MIRROR_DEBIAN_INSTALLER="${LB_PARENT_MIRROR_DEBIAN_INSTALLER:-${LB_MIRROR_CHROOT}}"
--- live-build-4.0.4.orig/scripts/build/chroot_archives
+++ live-build-4.0.4/scripts/build/chroot_archives
@@ -160,11 +160,11 @@ EOF
debian)
if [ "${LB_PARENT_DISTRIBUTION}" != "sid" ]
then
- echo "deb ${LB_PARENT_MIRROR_CHROOT} ${LB_PARENT_DISTRIBUTION}-backports ${LIVE_IMAGE_PARENT_ARCHIVE_AREAS}" >> chroot/etc/apt/${_PARENT_FILE}
+ echo "deb ${LB_PARENT_MIRROR_CHROOT_BACKPORTS} ${LB_PARENT_DISTRIBUTION}-backports ${LIVE_IMAGE_PARENT_ARCHIVE_AREAS}" >> chroot/etc/apt/${_PARENT_FILE}
if [ "${_PASS}" = "source" ] || [ "${LB_APT_SOURCE_ARCHIVES}" = "true" ]
then
- echo "deb-src ${LB_PARENT_MIRROR_CHROOT} ${LB_PARENT_DISTRIBUTION}-backports ${LIVE_IMAGE_PARENT_ARCHIVE_AREAS}" >> chroot/etc/apt/${_PARENT_FILE}
+ echo "deb-src ${LB_PARENT_MIRROR_CHROOT_BACKPORTS} ${LB_PARENT_DISTRIBUTION}-backports ${LIVE_IMAGE_PARENT_ARCHIVE_AREAS}" >> chroot/etc/apt/${_PARENT_FILE}
fi
fi
;;
@@ -172,11 +172,11 @@ EOF
if [ "${LB_DERIVATIVE}" = "true" ]
then
-echo "deb ${LB_MIRROR_CHROOT} ${_DISTRIBUTION}-backports ${LB_ARCHIVE_AREAS}" >> chroot/etc/apt/sources.list.d/${LB_MODE}.list
+echo "deb ${LB_MIRROR_CHROOT_BACKPORTS} ${_DISTRIBUTION}-backports ${LB_ARCHIVE_AREAS}" >> chroot/etc/apt/sources.list.d/${LB_MODE}.list
if [ "${_PASS}" = "source" ] || [ "${LB_APT_SOURCE_ARCHIVES}" = "true" ]
then
- echo "deb-src ${LB_MIRROR_CHROOT} ${_DISTRIBUTION}-backports ${LB_ARCHIVE_AREAS}" >> chroot/etc/apt/sources.list.d/${LB_MODE}.list
+ echo "deb-src ${LB_MIRROR_CHROOT_BACKPORTS} ${_DISTRIBUTION}-backports ${LB_ARCHIVE_AREAS}" >> chroot/etc/apt/sources.list.d/${LB_MODE}.list
fi
fi
fi
@@ -652,11 +652,11 @@ EOF
debian)
if [ "${LB_PARENT_DISTRIBUTION}" != "sid" ]
then
- echo "deb ${LB_PARENT_MIRROR_BINARY}
Bug#820514: crafty: Please package latest upstream 25.0.1
why this can be done in so time? if need i can provide dsc sources from my personal opensuse build service Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com
