Bug#1020519: cyrus-imapd: Permission problem sending redirect email from sieve rule

[Libor Klepáč]

Version: 3.2.6-2+deb11u2

Sorry, it's on Debian Bullseye , i filled the report from my machine
and forgot to change the version

Libor

Bug#1020519: cyrus-imapd: Permission problem sending redirect email from sieve rule

[Libor Klepáč]

Source: cyrus-imapd
Version: 3.6.0~beta2-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

We have problems sending redirect emails using sieve filter.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

When sieve sends email, it spawns 
/usr/lib/postfix/sbin/smtpd
under user cyrus.
Problem is, we use proxymap in our postfix setting (users in mariadb).

And so it needs access to socket /var/spool/postfix/private/proxymap which is 
only accessible by user/group postfix.
So i added user cyrus to group postfix.

Next problem is, that directory /var/spool/postfix/private/ is only accessible 
by user postfix.
So i added changed rights to 710 and chgrp-ed it to postfix

Now, i can forward emails from sieve, but i don't like it and don't know, if it 
survives reboot/package upgrade.

Can this be somehow addressed from cyrus side?

Thanks for info,
Libor



- -- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-17-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cyrus-imapd depends on:
ii  cyrus-common  3.2.6-2+deb11u2
ii  libc6 2.31-13+deb11u4
ii  libcom-err2   1.46.2-2
ii  libsasl2-22.1.27+dfsg-2.1+deb11u1
ii  libssl1.1 1.1.1n-0+deb11u3
ii  libwrap0  7.6.q-31
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

Versions of packages cyrus-imapd recommends:
ii  rsync  3.2.3-4+deb11u1

cyrus-imapd suggests no packages.

- -- Configuration Files:
/etc/pam.d/imap changed:
@include common-auth-mail
@include common-account-mail


-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAmMshKUVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOCVgP/1OjSpXSGA4L1TXcwvX+H3tWEclm
lCTObrRLxckCvHUZt1o6IDBR8nzDryTdv+oUzjLihitDtdg4SUJXyltxY8lkF5X7
QT/r90vJF6o8dOwQakKvKrP9ENkX9bUx7jA1YDWfbSX4tA+ZcS0qMRSG8oLi/z7K
cm/69DyG/hEv3RMiinIo6p1RB9MFI2eloK5HgFc1UoO36PExvtqpS0s7xAlhYXJL
b0Aun5YqYAcdHsl+EveZkhIBFYAkR+YUyh5ZY4g5b49AQaQBBIxcUwTBLhYiwwv5
/SEFQBr8ij8uUzgkU8ujzTN67Gpn1MEXCF/n1eqQ5rZzs8eNhYYvc3q3oVEf6H3K
3L/ipn5yBQVD1I+R86fBb+YvCIMR/c/h3YvHwjlDm7KNS90nPNAkT8z8pPZXjTaR
WQ8Iv0Vsx6TuEgpNuxNOGsjmDZ35My6vvtIkYvsK6mzUjsEnxQ3X+ORWknsS2mvt
+nZDbuiSMs7n9cEy9CvoGrbPNJeO0AGWGJjAIrNjOebV+ZngmLCRgkFjQClUdr53
pQ+50+twoKnPrfHFnGKwJQM+keooq2NMvJ37sQWuZSLIHoR0oRewlvCPio8z8cvF
j5ZEEXeqiYF8GrOinxcpWYa9vF/hVoAR1Zjn8/gM4GJuih6dETJYWlR50d8MkQ+P
35RIJ9Xs09KE348K
=pEkn
-END PGP SIGNATURE-

Bug#1020453: docker.io: consider backporting to stable

[Libor Klepáč]

Package: docker.io
Followup-For: Bug #908603

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello Maintainers,
could you please consider backporting docker.io version 20.10.17 to stable?

We are hitting problem with graylog docker image.
https://github.com/Graylog2/graylog-docker/issues/217

Solution seems to be using docker at least in version 20.10.10 or running with 
seccomp=unconfirmed.

Unfortunately it's not possible to use package from testing due to libc6 
dependency.

Thanks for answer,
Libor


- - -- System Information:
Debian Release: bookworm/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages docker.io depends on:
ii  adduser3.129
ii  containerd 1.6.8~ds1-1
ii  init-system-helpers1.65.2
ii  iptables   1.8.8-1
ii  libc6  2.34-8
ii  libdevmapper1.02.1 2:1.02.185-1
ii  libsystemd0251.4-3
ii  lsb-base   11.4
ii  runc   1.1.4+ds1-1
ii  sysvinit-utils [lsb-base]  3.05-6
ii  tini   0.19.0-1

Versions of packages docker.io recommends:
ii  apparmor 3.0.7-1
ii  ca-certificates  20211016
pn  cgroupfs-mount   
ii  git  1:2.37.2-1
ii  needrestart  3.6-2
ii  xz-utils 5.2.5-2.1

Versions of packages docker.io suggests:
pn  aufs-tools 
ii  btrfs-progs5.19-1
ii  debootstrap1.0.127
pn  docker-doc 
ii  e2fsprogs  1.46.6~rc1-1
pn  rinse  
pn  rootlesskit
ii  xfsprogs   5.19.0-1
pn  zfs-fuse | zfsutils-linux  

- - -- no debconf information

- -BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAmMrdNcVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOQlcQAJnjO7FRqOtHOPUDNrW7SYMfsmIt
tnUOCqD7vISHhcRRLVsItUw9eRcLcUk6RPuuYU/3Big5Fn0ADR0WfaNHBxKZsnoD
6RZCetX8NGEIlNP1ZEEMfVoXWl3qePW+TCXRKt2IHMvKOPWuyjykV5gnnTwUyqnO
VfVaVmdda7PT4xhmAzWOuEfAYZu7m1qzeKw4l1vs0BestTVcRCkWDYl+1EPQmZO/
9tE8mHsiDdm1imLlS/X1kawmTBDFZiTreF1Ft19t69Dy5DvQBg2dwpcXVPRiea1E
EjdiHho3I2aPwLFVIv7OFqzpMK+zt1V9nQExUgp245zCmy2GxcLqtoMokWazC2jN
EP//r3MwbukQklzRr7+IN3AtjP7EIUAJzV+CcBYrgjq3HDxEIh1F1KYyC6qNkmGh
XK7FLBHrWIh0epFou47/yrzUYF8TVNlPgVSZENpNSS3A/snNnZPEj1nNbVvHQaXJ
UBddzC0bDAmcxj1ZOmHhfG/IGWxJHMBJQoq6fZbtmNUnY9BHb0EZJtVupFzIppW1
r2527kgnnfS9bHM68hrN8ur3rogZsY5u73a+Rz+UcL+g5r18oP2CoJmJr0I1+As0
L8w8psD95d73jEDryKW4+LrrVpQIOFXfa9E0WC4fbsp5GvNdDdRzVxGa61+55o43
VC4ZEVuFYImmlw+n
=XBaB
- -END PGP SIGNATURE-

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAmMrdSIVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOj1MP/jgmHT8nfNJ7HXJXAgJw/nHwoIh0
QoTiS2u9tC804iZ9HvvNrXF+0CBeFFCOVzWlN+hcabgPnA1xY6byYXvHK1o6477W
MK5RXmqX2uqgmbJG0RAJlpraEty2lElTC0B3EvIIypy2TnSTS8D38bS2fN6021j9
dpYyLhZPcxIpR9QhYI20fTW3Okkp6thSiz5UDWpAw4/yHLt16Boh/vDHhAVa/mms
3SELHScThXsuCCzHYVfPW2p7UoKul61oWLsb6QmUhajeOzEC4hb6og61HrdKv4iN
1iYnRgvqid97CPgC4ZK4b0PleVTcFJlxEKtI75IOzXimaRHU9PHNBRf8udJ+hQTI
TB/1rJwWHdjBOlEx1ChVPSXjHKtmB83GQblsWeHMt8q+OQCjl9u72k4hhY+LK9JC
z7rioIjH338QETppasJBYKnvnOiBDvOlAgJUB4PPwr0lUlLcKcVYRhgymU2KZ2Nk
d1g9c3svt4BCT+wmIZTzeCyhN6eZVHdCk2DKbv7hd5d9+mTIaiiL42wCYmCL/C4J
3WaVkmn8qCzVdgu0wxzmW/k3Ed9py9xZySr095hW9GbR9AroGHoKg4Wr/Z/P04V9
bpnWBlSP/UiLwxR+mApSNNDneb9g4DxgnLKpXpUSI42e372MaExHzFRYlXVyH3ii
qHBdiUOkgxpckqtS
=jnYv
-END PGP SIGNATURE-

Bug#1010842: Info received (fail2ban not starting proftpd and sshd jails correctly)

[Libor Klepáč]

Hi,
is it possible, that iptables chains are created only when needed (ie.
only when some ip should be banned?)

Libor

On St, 2022-05-11 at 12:15 +, Debian Bug Tracking System wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due
> course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian Python Team 
> 
> If you wish to submit further information on this problem, please
> send it to 1010...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

Bug#990256: BackupPC_deleteFile needs missing modules

[Libor Klepáč]

Hi,
according to answer to my question
https://sourceforge.net/p/backuppc/mailman/backuppc-users/thread/25340.59119.354404.690924%40consult.pretender/#msg37694602

BackupPC_deleteFile cannot by used with backuppc4 without complete
rewrite.
I think, it should be dropped from package (also jLib.pm?)

You can use new script BackupPC_backupDelete instead

With regards,

Libor

Bug#1010842: fail2ban not starting proftpd and sshd jails correctly

[Libor Klepáč]

Hi,
i forgot to paste output of ipset, only one ipset is created

# ipset list -n | grep f2b
f2b-firehol


Libor

Bug#1010842: fail2ban not starting proftpd and sshd jails correctly

[Libor Klepáč]

Package: fail2ban
Version: 0.11.2-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,
we have problem using fail2ban on proftpd and sshd jails on Debian Bullseye and 
Buster.
we have pretty simple/standard config, with proftpd jail enabled in our file 
/etc/fail2ban/jail.d/proftpd.conf

[proftpd]
enabled = true

Some hosts use default banaction, some use banaction with ipset.
We use iptables-legacy, because we use firehol for generating our firewall.

Problem is, proftpd and sshd jails are never registered in firewall, but 
fail2ban loads them. 
Some other jails are loaded and registered in firewall without problems 
(mostly...).
For example:

# iptables -L -n -v | grep f2b
 140K 8379K DROP   all  --  *  *   0.0.0.0/00.0.0.0/0   
 match-set f2b-firehol src

# fail2ban-client status 
Status
|- Number of jail:  3
`- Jail list:   firehol, proftpd, sshd

# fail2ban-client status proftpd 
Status for the jail: proftpd
|- Filter
|  |- Currently failed: 0
|  |- Total failed: 0
|  `- File list:/var/log/proftpd/proftpd.log
`- Actions
   |- Currently banned: 0
   |- Total banned: 0
   `- Banned IP list:

and this is in log

2022-05-11 12:51:09,596 fail2ban.jail   [732814]: INFOCreating new 
jail 'proftpd'
2022-05-11 12:51:09,596 fail2ban.jail   [732814]: INFOJail 
'proftpd' uses pyinotify {}
2022-05-11 12:51:09,596 fail2ban.filter [732814]: DEBUG   Setting 
usedns = warn for FilterPyinotify(Jail('proftpd'))
2022-05-11 12:51:09,596 fail2ban.filter [732814]: DEBUG   Created 
FilterPyinotify(Jail('proftpd'))
2022-05-11 12:51:09,599 fail2ban.filter [732814]: DEBUG   Setting 
usedns = warn for FilterPyinotify(Jail('proftpd'))
2022-05-11 12:51:09,599 fail2ban.server [732814]: DEBUG prefregex: 
'^(?:\\[\\])?\\s*(?:<[^.]+\\.[^.]+>\\s+)?(?:\\S+\\s+)?(?:kernel:\\s?\\[ 
*\\d+\\.\\d+\\]:?\\s+)?(?:@vserver_\\S+\\s+)?(?:(?:(?:\\[\\d+\\])?:\\s+[\\[\\(]?proftpd(?:\\(\\S+\\))?[\\]\\)]?:?|[\\[\\(]?proftpd(?:\\(\\S+\\))?[\\]\\)]?:?(?:\\[\\d+\\])?:?)\\s+)?(?:\\[ID
 \\d+ \\S+\\]\\s+)?\\S+ \\(\\S+\\[\\]\\)[: -]+ 
(?:USER|SECURITY|Maximum) .+$'
2022-05-11 12:51:09,601 fail2ban.filter [732814]: INFOAdded 
logfile: '/var/log/proftpd/proftpd.log' (pos = 3553, hash = 
621b6cc23a2073ed6173a4b7bff999ac9705b311)
2022-05-11 12:51:09,602 fail2ban.filterpyinotify[732814]: DEBUG   New  at 0x7fe14c092ca0> dir=True >
2022-05-11 12:51:09,602 fail2ban.filterpyinotify[732814]: DEBUG   Added monitor 
for the parent directory /var/log/proftpd
2022-05-11 12:51:09,602 fail2ban.filterpyinotify[732814]: DEBUG   New  at 0x7fe14c092ca0> dir=False >
2022-05-11 12:51:09,602 fail2ban.filterpyinotify[732814]: DEBUG   Added file 
watcher for /var/log/proftpd/proftpd.log
2022-05-11 12:51:09,602 fail2ban.filterpyinotify[732814]: MSG Log absence 
detected (possibly rotation) for /var/log/proftpd/proftpd.log, reason: INITIAL 
of /var/log/proftpd/proftpd.log
2022-05-11 12:51:09,602 fail2ban.CommandAction  [732814]: DEBUG Set name = 
'proftpd'
2022-05-11 12:51:09,611 fail2ban.jail   [732814]: DEBUG   Starting jail 
'proftpd'
2022-05-11 12:51:09,611 fail2ban.filterpyinotify[732814]: DEBUG   [proftpd] 
filter started (pyinotifier)
2022-05-11 12:51:09,611 fail2ban.filterpyinotify[732814]: MSG Log presence 
detected for file /var/log/proftpd/proftpd.log
2022-05-11 12:51:09,611 fail2ban.jail   [732814]: INFOJail 
'proftpd' started
2022-05-11 12:51:23,025 fail2ban.jail   [732814]: DEBUG   Stopping jail 
'proftpd'
2022-05-11 12:51:23,025 fail2ban.filter [732814]: INFORemoved 
logfile: '/var/log/proftpd/proftpd.log'
2022-05-11 12:51:23,025 fail2ban.filterpyinotify[732814]: DEBUG   Removed file 
watcher for /var/log/proftpd/proftpd.log
2022-05-11 12:51:23,025 fail2ban.filterpyinotify[732814]: DEBUG   Removed 
monitor for the parent directory /var/log/proftpd
2022-05-11 12:51:23,127 fail2ban.filterpyinotify[732814]: DEBUG   [proftpd] 
filter exited (pyinotifier)
2022-05-11 12:51:23,628 fail2ban.actions[732814]: NOTICE  [proftpd] 
Flush ticket(s) with iptables-ipset-proto6-drop
2022-05-11 12:51:23,628 fail2ban.actions[732814]: DEBUG Unbanned 0, 
0 ticket(s) in 'proftpd'
2022-05-11 12:51:23,628 fail2ban.actions[732814]: DEBUG   proftpd: 
action iptables-ipset-proto6-drop terminated
2022-05-11 12:51:23,629 fail2ban.filterpyinotify[732814]: DEBUG   [proftpd] 
filter terminated (pyinotifier)
2022-05-11 12:51:23,629 fail2ban.jail   [732814]: INFOJail 
'proftpd' stopped
2022-05-11 12:51:23,765 fail2ban.jail   [733102]: INFOCreating new 
jail 'proftpd'
2022-05-11 12:51:23,765 fail2ban.jail   [733102]: INFOJail 
'proftpd' uses pyinotify {}
2022-05-11 12:51:23,773 fail2ban.filter [733102]: INFOAdded 
logfile: '/var/log/proftpd/proftpd.log' (pos = 3553, hash = 
621b6cc23a2073ed6173a4b7bff999ac9705b311)
2022-05-11 

Bug#976014: firehol: Role of /etc/default/firehol and START_FIREHOL variable

[Libor Klepáč]

Yeah,
i have added this to my "Upgrade to Debian 11 notes".
Maybe it deserves some news entry in package?

With regards,
Libor

Bug#985942: kodi: Cannot shutdown computer from kodi

[Libor Klepáč]

Hi,
after lots of debuging with Vasyl Gello (thanks!), it seems, everything
is ok on kodi package and system side, problem is probably with add-on
"Skin helper service" or "Embuary helper" - after disabling those two,
power related commands started to work

I will investigate more

Thanks,
Libor

Bug#985942: kodi: Cannot shutdown computer from kodi

[Libor Klepáč]

Package: kodi
Version: 2:19.0+dfsg1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,
after few weeks running kodi on bullseye, shutting down computer from kodi 
stopped working.

I run kodi from ~/.xsession using autologin in lightdm autogreeter, using 
dedicated user.

Few weeks ago i upgraded from buster to bullseye, to get kodi 19.
Everything was working ok.

Since this week (i think), I cannot shutdown/restart computer from kodi.

Trying to fix it:
- - I switched from running kodi to kodi-standalone in .xsession.
- - I switched from running default session to kodi.session (using 
autologin-session=kodi in lightdm config)
- - I noticed that lightdm suggests upower and accountsservices, i installed it.
- - I disable plymouth (by taking out "splash" from grub arguments), which i 
enabled recently.
- - I tried to provide polkit file from 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863483 , 
https://forum.kodi.tv/showthread.php?tid=165707

After every change, i rebooted. Still no luck shutting down the computer from 
kodi.

Sometimes, it just quits kodi, but it is started again by lightdm.

Thanks,
Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAmBd8mMVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eO/UsQAJzGTARtaGXy2HYbRV4XvuezogW2
4mRnIojvj/dMdUEg4nyb3m/Lehn3YL8IqPM+kA3ebAE5tmPDEw2+Db1G7J1d+ecF
4S6F9KiderXg5dKfk8Zk4esnBkFyAHEVpfFZAKHpeT0ApIHdlw5w9GZgqKhjHc5B
v0TPy9JKOj+zsZFYdMKX4v374VHmDLWuPM+PBnDuzI91tTOW2FGy4JcwvMwxnrId
cbIF3LqmRUJRTCw3JWspmTDDZ5nwRjHuDE41RNqOyLrAVq+CpmTWvE+giRhRvXZE
+PnboDyCMxcTqQUYl7H6Cs9iGxRpAdd80r60gVMOKFTtXfEqN7kNXBM364gcxIqx
ZcYOraujFLaolte25BxTdeB6Rr3XbgHhiSv0nKzN43h2NulhclaCwUvnjhPvQJx6
A47Ya2PnGzv7NdQP9nwgY4BQFeTpzUXMMRJtlyBtWAeV9kCqUpOhtYDEJpiLA65r
yC0P7/oCmf3s4XKS3J1mhIELq5lkdz86nJLmll4YDrXqUhTkn6Ajc6xhTA9eUDAj
GjQ9XRXlbLB+MDHX9IQ6ShhwGaMCXkYc8nLdCFJm7qC4bpFqgEHsra+CqGRNy8TD
TS/1qTQgqSCY+c2i6ZncCTM8J4fash5rN2xwWuQnQOL8wjjGWSBGydhKWGHRm1Gb
B2UzC6HT19S8kKM5
=uGNg
-END PGP SIGNATURE-

Bug#925606: gitlab: Fail to upgrade (error with activesupport gem)

[Libor Klepáč]

Sorry,
it was because i was running it by hand for this email and did not set
RAILS_ENV

It fails with different error when I set RAILS_ENV to production

Libor

$ bundle exec rake db:migrate --trace
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Attention: used pure ruby version of MurmurHash3
** Invoke db:migrate (first_time)
** Invoke db:load_config (first_time)
** Invoke environment (first_time)
** Execute environment
/usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized
constant Gitlab::COM_URL
/usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of
COM_URL was here
/usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized
constant Gitlab::APP_DIRS_PATTERN
/usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of
APP_DIRS_PATTERN was here
/usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized
constant Gitlab::SUBDOMAIN_REGEX
/usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of
SUBDOMAIN_REGEX was here
/usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized
constant Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of
VERSION was here
/usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized
constant Gitlab::INSTALLATION_TYPE
/usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of
INSTALLATION_TYPE was here
/usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized
constant Gitlab::HTTP_PROXY_ENV_VARS
/usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of
HTTP_PROXY_ENV_VARS was here
/usr/share/gitlab/config/initializers/2_app.rb:6: warning: already
initialized constant Gitlab::VERSION
/usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of
VERSION was here
rake aborted!
NoMethodError: undefined method `rails5?' for Gitlab:Module
/usr/share/gitlab/config/initializers/mysql_set_length_for_binary_index
es.rb:27:in `'
/usr/share/rubygems-integration/all/gems/activesupport-
5.2.3/lib/active_support/dependencies.rb:285:in `load'
/usr/share/rubygems-integration/all/gems/activesupport-
5.2.3/lib/active_support/dependencies.rb:285:in `block in load'
/usr/share/rubygems-integration/all/gems/activesupport-
5.2.3/lib/active_support/dependencies.rb:257:in `load_dependency'
/usr/share/rubygems-integration/all/gems/activesupport-
5.2.3/lib/active_support/dependencies.rb:285:in `load'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:657:in `block in load_config_initializer'
/usr/share/rubygems-integration/all/gems/activesupport-
5.2.3/lib/active_support/notifications.rb:170:in `instrument'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:656:in `load_config_initializer'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:614:in `block (2 levels) in '
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:613:in `each'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:613:in `block in '
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/initializable.rb:32:in `instance_exec'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/initializable.rb:32:in `run'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/initializable.rb:61:in `block in run_initializers'
/usr/lib/ruby/2.5.0/tsort.rb:228:in `block in tsort_each'
/usr/lib/ruby/2.5.0/tsort.rb:350:in `block (2 levels) in
each_strongly_connected_component'
/usr/lib/ruby/2.5.0/tsort.rb:422:in `block (2 levels) in
each_strongly_connected_component_from'
/usr/lib/ruby/2.5.0/tsort.rb:431:in
`each_strongly_connected_component_from'
/usr/lib/ruby/2.5.0/tsort.rb:421:in `block in
each_strongly_connected_component_from'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/initializable.rb:50:in `each'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/initializable.rb:50:in `tsort_each_child'
/usr/lib/ruby/2.5.0/tsort.rb:415:in `call'
/usr/lib/ruby/2.5.0/tsort.rb:415:in
`each_strongly_connected_component_from'
/usr/lib/ruby/2.5.0/tsort.rb:349:in `block in
each_strongly_connected_component'
/usr/lib/ruby/2.5.0/tsort.rb:347:in `each'
/usr/lib/ruby/2.5.0/tsort.rb:347:in `call'
/usr/lib/ruby/2.5.0/tsort.rb:347:in `each_strongly_connected_component'
/usr/lib/ruby/2.5.0/tsort.rb:226:in `tsort_each'
/usr/lib/ruby/2.5.0/tsort.rb:205:in `tsort_each'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/initializable.rb:60:in `run_initializers'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/application.rb:361:in `initialize!'
/usr/share/gitlab/config/environment.rb:6:in `'

Bug#925606: gitlab: Fail to upgrade (error with activesupport gem)

[Libor Klepáč]

Hi,
i'm trying to upgrade to gitlab 12.6.2-1 from 11.3.11+dsfg-1.

I get this error on db:migrate
I fails on:
$ bundle exec rake db:migrate --trace
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
Attention: used pure ruby version of MurmurHash3
rake aborted!
NameError: uninitialized constant RSpec
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/active_supp
ort.rb:53:in `block in load_missing_constant'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/active_supp
ort.rb:8:in `without_bootsnap_cache'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/active_supp
ort.rb:53:in `rescue in load_missing_constant'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/active_supp
ort.rb:42:in `load_missing_constant'
/usr/share/gitlab/lib/tasks/frontend.rake:4:in `block in '
/usr/lib/ruby/vendor_ruby/rake/task_manager.rb:225:in `in_namespace'
/usr/lib/ruby/vendor_ruby/rake/dsl_definition.rb:141:in `namespace'
/usr/share/gitlab/lib/tasks/frontend.rake:2:in `'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_requ
ire.rb:50:in `load'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_requ
ire.rb:50:in `load'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:650:in `block in run_tasks_blocks'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:650:in `each'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:650:in `run_tasks_blocks'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/application.rb:515:in `run_tasks_blocks'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:459:in `load_tasks'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/railtie.rb:190:in `public_send'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/railtie.rb:190:in `method_missing'
/usr/share/gitlab/Rakefile:10:in `'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:703:in
`raw_load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:104:in `block in
load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in
`standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:103:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:82:in `block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in
`standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:80:in `run'
/usr/bin/rake:27:in `'

Caused by:
NameError: uninitialized constant RSpec
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/active_supp
ort.rb:43:in `load_missing_constant'
/usr/share/gitlab/lib/tasks/frontend.rake:4:in `block in '
/usr/lib/ruby/vendor_ruby/rake/task_manager.rb:225:in `in_namespace'
/usr/lib/ruby/vendor_ruby/rake/dsl_definition.rb:141:in `namespace'
/usr/share/gitlab/lib/tasks/frontend.rake:2:in `'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_requ
ire.rb:50:in `load'
/usr/lib/ruby/vendor_ruby/bootsnap/load_path_cache/core_ext/kernel_requ
ire.rb:50:in `load'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:650:in `block in run_tasks_blocks'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:650:in `each'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:650:in `run_tasks_blocks'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/application.rb:515:in `run_tasks_blocks'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/engine.rb:459:in `load_tasks'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/railtie.rb:190:in `public_send'
/usr/share/rubygems-integration/all/gems/railties-
5.2.3/lib/rails/railtie.rb:190:in `method_missing'
/usr/share/gitlab/Rakefile:10:in `'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load'
/usr/lib/ruby/vendor_ruby/rake/rake_module.rb:29:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:703:in
`raw_load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:104:in `block in
load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in
`standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:103:in `load_rakefile'
/usr/lib/ruby/vendor_ruby/rake/application.rb:82:in `block in run'
/usr/lib/ruby/vendor_ruby/rake/application.rb:186:in
`standard_exception_handling'
/usr/lib/ruby/vendor_ruby/rake/application.rb:80:in `run'
/usr/bin/rake:27:in `'



In this bugreport, you suggest gitlab should conflict with ruby-
bootsnap, but it depends on it.
Is there 

Bug#941889: kde-spectacle: Segfaults while saving rectangular selection screenshot

[Libor Klepáč]

Package: kde-spectacle
Version: 19.08.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,
since upgrading from previous version, i cannot do rectangular snapshots with 
spectacle.
Snapshot is taken, but spectacle crashes when i click "save" or "copy to 
clipboard" buttons.
Snapshoting whole window/whole screen is ok, no crash.

This is crash report, is it useful?

Thanks, 
Libor

Application: Spectacle (spectacle), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f30755df800 (LWP 14982))]

Thread 4 (Thread 0x7f306bfff700 (LWP 14985)):
#0  0x7f30788a0db5 in pthread_cond_wait@@GLIBC_2.3.2 () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f3070a1cffb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#2  0x7f3070a1cc17 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#3  0x7f307889afb7 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#4  0x7f3079ab22ef in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f307305e700 (LWP 14984)):
#0  0x7f3079aa38bc in read () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f3077cffcbf in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3077cb8bfe in g_main_context_check () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3077cb9052 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3077cb91cf in g_main_context_iteration () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f307a00e3e3 in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f3079fbbcfb in 
QEventLoop::exec(QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f3079e0bd8e in QThread::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f307a7ee545 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x7f3079e15a07 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f307889afb7 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#11 0x7f3079ab22ef in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f307479b700 (LWP 14983)):
#0  0x7f3079aa7d2f in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7f307b50acf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f307b50c91a in xcb_wait_for_event () from 
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f3074f04d79 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f3079e15a07 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f307889afb7 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#6  0x7f3079ab22ef in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f30755df800 (LWP 14982)):
[KCrash Handler]
#6  0x7f3079a3e926 in malloc () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x7f3079e164b2 in QArrayData::allocate(unsigned long, unsigned long, 
unsigned long, QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f3079e18465 in QByteArray::reallocData(unsigned int, 
QFlags) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f307a8a6850 in ?? () from 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#10 0x7f307a8a70ea in ?? () from 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#11 0x7f307a8a73f7 in ?? () from 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#12 0x7f307a8aabb0 in ?? () from 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#13 0x7f307a88fc5c in KConfig::sync() () from 
/usr/lib/x86_64-linux-gnu/libKF5ConfigCore.so.5
#14 0x5639904cf3d9 in ?? ()
#15 0x7f307ab3eefe in QWidget::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#16 0x7f307ab00501 in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7f307ab079b0 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f3079fbd029 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x7f307ab5bb5f in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x7f307ab00501 in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f307ab079b0 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x7f3079fbd029 in QCoreApplication::notifyInternal2(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f307a364966 in 
QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*)
 () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#24 0x7f307a369f6d in 
QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
 () from 

Bug#926784: firehol: Please document usage of iptables-legacy

[Libor Klepáč]

Hi,
just a follow up from today.

On host, where I was debuging firehol behaviour on iptables-nft vs. iptables-
legacy (before reporting bug) , I got strange behavior after upgrading to 
3.1.6+ds-8.

It was caused by my manual change of iptables alternatives -legacy one.

Sequence was like this:
install firehol 3.1.6+ds-7
setup firewall (loaded do nft tables)
do some debuging to find out that you need -legacy
update-alternatives to iptables-legacy
load firewall again (this time, it loads to legacy iptables)
upgrade to firehol 3.1.6+ds-8, keep iptables alternatives to -legacy

Now you have two "identical" firewalls ;) - first was loaded with old version 
of firehol to nft, second is loaded to legacy tables.

Now change config of firehol, open new port to be accessible, reload firehol 
and test it.
It's not accessible, iptables keep logging dropped packet.

Try to allow all access, try to stop firehol - port is still not accessible.

List your firewall using iptables -L 

You see empty ruleset with policy=ACCEPT in all chains.

Go crazy ;)

Try to list 
iptables-nft -L

AHA - here is your firewall blocking your access. (it also warns you, that 
there are some rules in legacy tables)

Reboot

I think, users are safe to upgrade from -7 to -8 , unless they did manual 
override of iptables alternatives.

Libor

Bug#926865: ifupdown-extra: please fix apring redir

[Libor Klepáč]

Package: ifupdown-extra
Version: 0.28
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
can you please consider including this patch, to silence error on output 
redirect?

# LANG=C ifup eth2
/etc/network/if-up.d/10check-duplicate-ip: 88: 
/etc/network/if-up.d/10check-duplicate-ip: cannot create >/dev/null: Directory 
nonexistent
<27>Apr 11 15:02:42 root[27918]: ERROR: Duplicate address 192.168.208.24 
assigned in the network where eth2 is connected to.

Thanks,
Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlyvOy8VHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eORsAP/3c9z52Xr4B9d2uSiiYkTZaCL0ZB
KE27crVtyMxakXMLQ7QuQDDUWCGwoE4dPpimxcl2X+I3qqndmpDQBhKC6sbTL9hM
HHStZAJo51vXRXlkoXH9gVElKFPHBjiAT4I1XanzKlq5qV1RxFT5uVcv7ZhXGc16
m7ueb9z/7WrhUMmM8wNE+FKUhLQxVVNWW2LWlaRxXiPN5HqIIy9H/zNxlbiGy4xm
Ub2UeTao/rNxwot3VPGBsy/g+uItlHOOdXEpCHHYixHIVA2oMffqEvZaHpy/xhN0
LDrg3149x7ZRygD1VUZ7IfbAxIOS3kPIgftgvssI6v+GsZ2U+A1UeTQ1f4eg8D5F
zNMwPqR1mm4ktdYT8eJrA9oCorL6tTvLk4VB3hQazUtzbhYFh/517cLAGSzvVgYl
SRp8DBIe6BKASYdDNpyXwfgDh+79O4soKflZmxqcWO/wwf0I4LqPKbbnYsWLYzPJ
FoyHQc793+vGGiw6hg+oHgkuB2YWWomD86Q1inPwpJ9JY9p7ONo24XZdoFTmD3ch
5xDVuJr4gHV07BBFfWWvoJ82n/unByQDPfeSalwH/Kj8p2/ax6+/zOqQhwXGYVR9
qhhjeVWt/AXp89EovvPkRN5+8LYCet67ba1Y0noDt9obrpcQO1neMmxjQiH9MZBx
RK6+AwY1OxiCeBdF
=h3GX
-END PGP SIGNATURE-
diff -ur a/if-up-scripts/check-duplicate-ip b/if-up-scripts/check-duplicate-ip
--- a/if-up-scripts/check-duplicate-ip  2018-02-06 22:04:56.0 +0100
+++ b/if-up-scripts/check-duplicate-ip  2019-04-11 15:00:00.576916162 +0200
@@ -121,7 +121,7 @@
 ARP_TIMEOUT=${ARP_TIMEOUT:-1500} # Time here is measures in 
milliseconds
  # experiments show anything less than 
1500 is unreliable.
 ARPING_EXTRAOPTS=""  # No '-q' option in arping
-ARPING_REDIR=">/dev/null"# Send output to /dev/null if using 
this program
+ARPING_REDIR="/dev/null"# Send output to /dev/null if using 
this program
 else
 # Do not continue if ARPING is not available
 echo "WARNING: Cannot check for duplicate IP address in the network. 
The script cannot find the 'arping' program (tried /usr/bin/arping and 
/usr/sbin/arping. Please either install the iputils-arping or arping packages 
or disable this test by setting DO_ARPING to 'no' in $DEFAULT ." >&2

Bug#926784: firehol: Please document usage of iptables-legacy

[Libor Klepáč]

Hi,
usage of -legacy variant can be patched in during build time.

Included patch tested by manual running (i don't have disk space to install 
tex) of: 
./autogen.sh && ./configure && make 

and checking generated ./sbin/install.config


Libor
Description: compatibility with iptables-legacy
Author: libor.kle...@bcom.cz
Origin: other
Last-Update: 2019-04-10
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
Index: firehol-3.1.6+ds/configure.ac
===
--- firehol-3.1.6+ds.orig/configure.ac
+++ firehol-3.1.6+ds/configure.ac
@@ -189,7 +189,7 @@ if test x"$enable_firehol_wizard" = xyes
 AX_NEED_PROG([IP], [ip], [])
 fi
 if test x"$enable_ipv6" = xyes; then
-AX_CHECK_PROG([IP6TABLES], [ip6tables], [])
+AX_CHECK_PROG([IP6TABLES], [ip6tables-legacy], [])
 fi
 if test x"$enable_ipv6" = xyes; then
 AX_CHECK_PROG([IP6TABLES_RESTORE], [ip6tables-restore], [])
@@ -200,7 +200,7 @@ fi
 AX_CHECK_PROG([IPRANGE], [iprange], [])
 AX_CHECK_PROG([IPSET], [ipset], [])
 if test x"$enable_ipv4" = xyes; then
-AX_CHECK_PROG([IPTABLES], [iptables], [])
+AX_CHECK_PROG([IPTABLES], [iptables-legacy], [])
 fi
 if test x"$enable_ipv4" = xyes; then
 AX_CHECK_PROG([IPTABLES_RESTORE], [iptables-restore], [])
debianization.patch
debianization-usrmerge-transition.patch
iptables-legacy.patch

Bug#926784: firehol: Please document usage of iptables-legacy

[Libor Klepáč]

Package: firehol
Version: 3.1.6+ds-7
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
firehol seems to have problem to reread rules in nofast mode when using 
iptables-nft.
See: https://github.com/firehol/firehol/issues/352

Here is part of output, it goes on to ERROR : # 30
# firehol nofast try  
FireHOL: Saving active firewall to a temporary file...  OK 
FireHOL: Processing file '/etc/firehol/firehol.conf'...  OK  (522 iptables 
rules)
FireHOL: Activating ipsets...  OK 
FireHOL: Activating new firewall (522 rules)... 

- - 

ERROR   : # 1.
WHAT: A runtime command failed to execute (returned error 1).
SOURCE  : 30@/etc/firehol/firehol.conf: blacklist4:
COMMAND : /usr/sbin/iptables -t filter -N BLACKLIST.bi.1.in 
OUTPUT  : 

iptables v1.8.2 (nf_tables): Chain already exists
- - 

ERROR   : # 2.
WHAT: A runtime command failed to execute (returned error 1).
SOURCE  : 30@/etc/firehol/firehol.conf: blacklist4:
COMMAND : /usr/sbin/iptables -t filter -N BLACKLIST.bi.1.out 
OUTPUT  : 

iptables v1.8.2 (nf_tables): Chain already exists
- - 


It can be solved by using iptables-legacy.

Can you please document this in NEWS entry?
Users of firehol should run
# update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
# update-alternatives --set iptables /usr/sbin/iptables-legacy

Thanks,
Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlytsyIVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOgscQAJQcq25XrIwxrIunE5QVP+BuKK9i
JIqyVvkIQEPVa10alut/UVPofkPiSS+VtG1Lhu5IkAt+WQsy54AFeyA0y8ujQpBE
lNqPIa6gj+fo1xOHk5YSlCZuUzVlpCDQ81/khUh3uCDJbV1ufOE306oJnG+LWGll
k9B5Tc/2OYZnukRncFstgdMD6surR2XFsI8mQwsTsI2fmPkjPaP1wCySMO4zW/Ku
HGD0tr2tImAg4x2HtzDQgztwIJnga9dpjtF+Y0Ww8TofLni8Tg5s7L1JRrbw9NB4
0E38tRr6R/49NiVtpYa1hKDsf8UYqRmtcWWBfUO28m7IhYFHu0+1KBuP2oAM8uC5
rdUaS2SdgdDH06JZ/Qq98AdG39RjmRuCyxK+uh8MAbnI/8ENE9DNAa/k5IcfvtY9
HRQkEB9PHzaLfPR1Qp4zEvrULH5eEw5GqIB8Qb/knYvgrIc8yh9eyj+t47qRy2N/
BX+7p8Ur38L5QRdppI3+ZfwCL0tUpBgVbfIHx02be4vtp1SExZvQv/KUbAnl17c8
kMPvzsH8rWkKxlFfT3hrl3plf/EtBci4bTzVy+UjZGnV87WH0YwZJ2noR4hMqAmt
QUidRqHQ580GhJNnIqD89GB96TCsgvO1jMhm2p9IpVPQbjFmJvtjKT4elpvTkCQZ
7wHmzTprFD+lEDrr
=HAh/
-END PGP SIGNATURE-

Bug#890877: gitlab: javascript locales not precompiled

[Libor Klepáč]

Package: gitlab
Version: 9.5.4+dfsg-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
it seems, that javascript locales are not precompiled before running webpack.
Upstream changed to yarn based build system and fixed it here.
https://gitlab.com/gitlab-org/gitlab-ce/commit/4c57d5ad188fe59e0c85798ccc4c81405652048c

You can run
bundle exec rake gettext:po_to_json 

before webpack to fix it.
Problem is, it needs to write to 
/usr/share/gitlab/app/assets/javascripts/locale/
So it must be set writeable by user gitlab or run as root.

Without this step, javascript is broken, it fails to load timeago.js, 
screenshot in attachement

Libor



-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlqL43MVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eO+PkP/iMIuG5VD5Z7+zIDfCmU2oyeJ7EU
nQ3YG3l42mtF1sQZQF289X0ZXkokZKWF7x7QVgmiTbpPxp6e8/EV9y08lQePYuuC
0zTfbUT56ug0DSz8IIgSndHAUUSfag/KigNbnsIIlY8YzkQq+E0hjNSoxEmYnq3E
Sz4rZttqLmisdGgZa9pdPivCOtEdJsAgssSoWo8CP9WeIML3syC4PXc0cUCCjkN9
nAHl/T4W5nJVRNo4GMBTdzTViy900MnAFuJkse0HqoW3lMXZ9Dx418Q3sk946Epl
FSZWeYX5P0MJVt6/DFiHkotREeK5+sMccdlRRRHYUtcyBYyYdHBWA/a0xZj6a2uH
hTFhxO8rEE+7RfKSqbXnubgTAZ/jrSuF4j3srRKw62+ZP+ZMnQzDoGFmppkkPnL3
N34y5lwaPRkDZpNx1Ronb1O6dj+WnGv1HcHpYh3qCvBYvcQHX+ySDNNbDz4rin8V
Xxk8FB8QgVU0fmpl/vWbN/W7yWFFyivzWAZAnAaGRFvRAw017oZnNHEH7SgP58h4
KEDimLhKoYD3Q/mZ4W7MNQ4Ag7eLgqW+1lvpvIES+IWe5Okl6Hnb+/lRTapm7WnD
90PQdqEFFPTCDmwk/KCVSE+k0vwlfiQB70texHCnUjEe1hqhPAMaMIrJKug3381/
NO6Tk6V2SCX2Q0gg
=Ktyx
-END PGP SIGNATURE-

Bug#890757: gitlab: Error 500 when issue has code block to render

[Libor Klepáč]

Package: gitlab
Version: 9.5.4+dfsg-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
when issue has some code block to render, there is error 500 in dashboard

Started GET "/dashboard/activity?limit=20=0" for x.x.x.x at 2018-02-18 
07:53:57 +0100
Processing by DashboardController#activity as JSON
  Parameters: {"limit"=>"20", "offset"=>"0"}
Completed 500 Internal Server Error in 586ms (ActiveRecord: 41.3ms)

ActionView::Template::Error (undefined method `html_escape' for 
#
Did you mean?  html_safe?):
10: .event-body
11:   .event-note
12: .md
13:   = event_note(event.target.note, project: event.project)
14: - note = event.target
15: - if note.attachment.url
16:   - if note.attachment.image?
  lib/banzai/renderer/html.rb:8:in `block_code'
  lib/banzai/filter/markdown_filter.rb:10:in `render'
  lib/banzai/filter/markdown_filter.rb:10:in `call'
  lib/banzai/pipeline/base_pipeline.rb:21:in `block (2 levels) in singleton 
class'
  lib/banzai/renderer.rb:107:in `render_result'
  lib/banzai/renderer.rb:138:in `block in cacheless_render'
  lib/gitlab/metrics/influx_db.rb:92:in `measure'
  lib/banzai/renderer.rb:137:in `cacheless_render'
  lib/banzai/renderer.rb:28:in `render'
  lib/banzai.rb:3:in `render'
  app/helpers/markup_helper.rb:220:in `markdown_unsafe'
  app/helpers/markup_helper.rb:79:in `markdown'
  app/helpers/markup_helper.rb:70:in `first_line_in_markdown'
  app/helpers/events_helper.rb:174:in `event_note'
  app/views/events/event/_note.html.haml:13:in 
`_app_views_events_event__note_html_haml___3195316608961436102_46994720833940'
  app/views/events/_event.html.haml:11:in 
`_app_views_events__event_html_haml__2698820872038661657_46994679561920'
  app/views/events/_events.html.haml:1:in 
`_app_views_events__events_html_haml___93854884984734810_46994679725040'
  app/controllers/application_controller.rb:234:in `pager_json'
  app/controllers/dashboard_controller.rb:17:in `block (2 levels) in activity'
  app/controllers/dashboard_controller.rb:12:in `activity'
  lib/gitlab/i18n.rb:46:in `with_locale'
  lib/gitlab/i18n.rb:52:in `with_user_locale'
  app/controllers/application_controller.rb:326:in `set_locale'
  lib/gitlab/middleware/multipart.rb:93:in `call'
  lib/gitlab/request_profiler/middleware.rb:14:in `call'
  lib/gitlab/middleware/go.rb:17:in `call'
  lib/gitlab/etag_caching/middleware.rb:11:in `call'
  lib/gitlab/request_context.rb:18:in `call'
  lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'

and isssue detail
Started GET "/group/project/issues/4097" for x.x.x.x at 2018-02-18 07:54:02 
+0100
Processing by Projects::IssuesController#show as HTML
  Parameters: {"namespace_id"=>"group", "project_id"=>"project", "id"=>"4097"}
Completed 500 Internal Server Error in 67ms (ActiveRecord: 21.6ms)

NoMethodError (undefined method `html_escape' for 
#
Did you mean?  html_safe?):
  lib/banzai/renderer/html.rb:8:in `block_code'
  lib/banzai/filter/markdown_filter.rb:10:in `render'
  lib/banzai/filter/markdown_filter.rb:10:in `call'
  lib/banzai/pipeline/base_pipeline.rb:21:in `block (2 levels) in singleton 
class'
  lib/banzai/renderer.rb:107:in `render_result'
  lib/banzai/renderer.rb:138:in `block in cacheless_render'
  lib/gitlab/metrics/influx_db.rb:92:in `measure'
  lib/banzai/renderer.rb:137:in `cacheless_render'
  lib/banzai/renderer.rb:49:in `cacheless_render_field'
  app/models/concerns/cache_markdown_field.rb:68:in `block in 
refresh_markdown_cache!'
  app/models/concerns/cache_markdown_field.rb:65:in `map'
  app/models/concerns/cache_markdown_field.rb:65:in `refresh_markdown_cache!'
  lib/banzai/renderer.rb:39:in `render_field'
  lib/banzai.rb:7:in `render_field'
  lib/banzai/object_renderer.rb:51:in `block in render_documents'
  lib/banzai/object_renderer.rb:50:in `map'
  lib/banzai/object_renderer.rb:50:in `render_documents'
  lib/banzai/object_renderer.rb:34:in `render'
  lib/banzai/note_renderer.rb:18:in `render'
  app/controllers/concerns/renders_notes.rb:5:in `prepare_notes_for_rendering'
  app/controllers/projects/issues_controller.rb:89:in `show'
  lib/gitlab/i18n.rb:46:in `with_locale'
  lib/gitlab/i18n.rb:52:in `with_user_locale'
  app/controllers/application_controller.rb:326:in `set_locale'
  lib/gitlab/middleware/multipart.rb:93:in `call'
  lib/gitlab/request_profiler/middleware.rb:14:in `call'
  lib/gitlab/middleware/go.rb:17:in `call'
  lib/gitlab/etag_caching/middleware.rb:11:in `call'
  lib/gitlab/request_context.rb:18:in `call'
  lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'

or saving new issue
Started POST "/root/test/issues" for x.x.x.x at 2018-02-18 13:50:08 +0100
Processing by Projects::IssuesController#create as HTML
  Parameters: {"utf8"=>"▒..", "authenticity_token"=>"[FILTERED]", 
"issue"=>{"title"=>"test", "description"=>"```\r\ntest\r\ntet\r\n```", 
"confidential"=>"0", "assignee_ids"=>["0"], "label_ids"=>[""], "due_date"=>"", 
"lock_version"=>""},
"namespace_id"=>"root", 

Bug#890333: gitlab: javascript errors after upgrade to 9.5.4

[Libor Klepáč]

Hi,
so running:
# npm install document-register-element@1.3.0
and 
# NODE_PATH=/usr/share/gitlab/node_modules webpack --config config/
webpack.config.js 

fixed second browser console error, javascript now loads, dashboard loads too

Thanks,

Libor


On středa 14. února 2018 13:05:16 CET Pirate Praveen wrote:
> On 02/14/2018 02:43 PM, Libor Klepáč wrote:
> > No luck, there is no jquery-atwho available in npm.
> > But i have downloaded version 1.5.4 of At.js and replaced files in
> > /usr/share/javascript/jquery-atwho
> > and one of errors disappeared.
> 
> This is a bug in libjs-jquery-atwho and I have reported it (#890391) and
> added a workaround for it in 9.5.4+dfsg-4.
> 
> You can try and install document-register-element@1.3.0 from npm (it is
> now 1.7.2). Or we may have a problem with our webpack.config.js or one
> of the webpack loaders.

Bug#890399: gitlab: override.conf in /etc/systemd/system/gitlab-*.service.d is not overwriten

[Libor Klepáč]

Here is little patch to migrate from override.conf to gitlab-user.conf in 
postinst.
Feel free to use or modify or discard ;)

Libor
diff -ur a/debian/postinst b/debian/postinst
--- a/debian/postinst	2018-02-14 12:52:35.904334762 +0100
+++ b/debian/postinst	2018-02-14 12:58:49.583882426 +0100
@@ -268,11 +268,15 @@
 path=/etc/systemd/system/gitlab-${service}.service.d
 mkdir -p $path
 if [ -e $path/override.conf ]; then
-  echo "$path/override.conf already exist"
+  # Disable user in override.conf
+  sed -i "s/^\( *\)\(User=.*\)/\1#\2/" $path/override.conf
+fi
+if [ -e $path/gitlab-user.conf ]; then
+  echo "$path/gitlab-user.conf already exist"
   # Make sure only gitlab user is updated
-  sed -i "s/^ *User=.*/User=$gitlab_user/" $path/override.conf
+  sed -i "s/^ *User=.*/User=$gitlab_user/" $path/gitlab-user.conf
 else
-  printf "[Service]\nUser=${gitlab_user}\n" > $path/override.conf
+  printf "[Service]\nUser=${gitlab_user}\n" > $path/gitlab-user.conf
 fi
   done
 

Bug#890399: gitlab: override.conf in /etc/systemd/system/gitlab-*.service.d is not overwriten

[Libor Klepáč]

Here is little patch to migrate from override.conf to gitlab-user.conf in 
postinst.
Feel free to use or modify or discard ;)

Libor
diff -ur a/debian/postinst b/debian/postinst
--- a/debian/postinst	2018-02-14 12:52:35.904334762 +0100
+++ b/debian/postinst	2018-02-14 12:58:49.583882426 +0100
@@ -268,11 +268,15 @@
 path=/etc/systemd/system/gitlab-${service}.service.d
 mkdir -p $path
 if [ -e $path/override.conf ]; then
-  echo "$path/override.conf already exist"
+  # Disable user in override.conf
+  sed -i "s/^\( *\)\(User=.*\)/\1#\2/" $path/override.conf
+fi
+if [ -e $path/gitlab-user.conf ]; then
+  echo "$path/gitlab-user.conf already exist"
   # Make sure only gitlab user is updated
-  sed -i "s/^ *User=.*/User=$gitlab_user/" $path/override.conf
+  sed -i "s/^ *User=.*/User=$gitlab_user/" $path/gitlab-user.conf
 else
-  printf "[Service]\nUser=${gitlab_user}\n" > $path/override.conf
+  printf "[Service]\nUser=${gitlab_user}\n" > $path/gitlab-user.conf
 fi
   done
 

Bug#890399: gitlab: override.conf in /etc/systemd/system/gitlab-*.service.d is not overwriten

[Libor Klepáč]

Package: gitlab
Version: 9.5.4.+dfsg-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
another problem. 
If admin creates for example:
/etc/systemd/system/gitlab-sidekiq.service.d/override.conf
by hand, changing properties other than User, then postinst script fails to 
update User property.
My file is
#[Service]
#Restart=always

so no User to change by sed inside postinst.

I don't know if some debian policy on naming such override files exists, but 
can you use for example
gitlab(-user).conf ? It is also parsed and included by systemd.

Also systemd doesn't like
EnvironmentFile=-/etc/default/gitlab
in /lib/systemd/system/gitlab-unicorn.service

service doesn't start because of
Feb 14 12:35:41 ms-gitlab systemd[1]: gitlab-unicorn.service: Ignoring invalid 
environment assignment 'for i in $(grep -v '#' /etc/gitlab/gitlab-debian.conf | 
cut -d=-f 1)': /etc/default/gitlab


Thanks,
Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlqEIHwVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOdhQQAJZ4dwoDavpwDz8m7+0JhbXyYOrz
CJYSC/Z9v5bQNvNqj771GXuWdwIxd3sAudwJShctYZWJA51d4gl9wPJ9WZf1FX70
kYrrsyWm48fyHv1BSsk4rbgbYGQ5Pc5yZx7L/ekbZohKf+2IR0fgg+nPxtJ5pxnG
g7/uIST+uQS3O66nRvkWccelnP/X0xIO/oiVAvCaI75Jj5YYx3ziyD9XyNx6NEoS
NwEy0QQdPvBfJvHq/qS30fDbtkMdP4YMi0mbqb32+FBq0yxt8MCKoYFWSBEqdPV+
VXyeFkMNXxJd6Z/lZoRDnVJXepmBdhowVDdj5a28EHrVra+8hCYiQO4/xurnEXPO
ACbFUFAgLOCC+9vyGe7fRZ2BpfeSmA/h1scPe9lXLE9WN2iyqlAmBO8RPLPTTcsd
VybEkzkb9RbpqFgrgbqfkBCcH7e+RAsySeJQiZA3XKcPG9VoefcqNq5rRSt5OxuI
0adii49pbRLjL493v73FdCC+6GnlDrdgi9XX6/jqwX6jg3ofwjXI5MCzWJ8jrdvW
94QX9qbs7NfY7EjBrKwrRnXzDRlMKAZENwCzoUYV8pR+FIRDOAiYCSdZT+48jdvQ
HPnCqSRNybeqMTTS1/yrMLZHtXDOtzP38nsVYFmsYZOQ5zMV7RGS84Pspf4aI6QV
DvgsPm8FpIEhPZ2e
=IcDF
-END PGP SIGNATURE-

Bug#890333: gitlab: javascript errors after upgrade to 9.5.4

[Libor Klepáč]

Hello,

On úterý 13. února 2018 16:40:03 CET Pirate Praveen wrote:
> On 02/13/2018 08:19 PM, Libor Klepáč wrote:
> > Package: gitlab
> > Version: 9.5.4.+dfsg-2
> > Severity: normal
> > 
> > Hello,
> > after upgrading gitlab from 8.13.x to 9.5.4 we get no events in dashboard
> > grids.
> Thanks for testing the new version. We need to fix this before uploading
> to unstable.
> 

> 
> You may want to try like this
> https://salsa.debian.org/ruby-team/gitlab/blob/master/debian/rake-tasks.sh#L
> 39
yes, this is in rake-tasks and i'm running it manualy, my sequence of commands 
was (if i remember correctly):
#(only once)
# npm install
# npm install indexof
# npm install randomfill

#repeated after each try
# NODE_PATH=/usr/share/gitlab/node_modules webpack \ 
--config config webpack.config.js
# bundle exec rake tmp:cache:clear assets:precompile


> > but it does not finish successfuly, complains about missing
> > webpack-stats-plugin, which seems to be installed.
> > 
> > Any clues what can be done?
> 
> Try replacing jquery.atwho.js with the version from npm. (npm install
> jquery-atwho, then webpack and asset precompile).

No luck, there is no jquery-atwho available in npm.

But i have downloaded version 1.5.4 of At.js and replaced files in 
/usr/share/javascript/jquery-atwho
and one of errors disappeared.

> 
> > This all bundler and node and webpack and etc. magic is ... (+ i have to
> > allow traffic to our protected network, for npm to work)
> We are getting very close to packaging all dependencies
> https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab
> 
> I'm stuck with https://github.com/facebook/react/issues/12076 any help
> on this is welcome.
Huh, i can see, this is frustrating.

Libor

Bug#890333: gitlab: javascript errors after upgrade to 9.5.4

[Libor Klepáč]

Package: gitlab
Version: 9.5.4.+dfsg-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
after upgrading gitlab from 8.13.x to 9.5.4 we get no events in dashboard grids.
Errors in firefox console  are
ReferenceError: Controller is not defined [Zjistit více]
common.bundle.js:19235:1
../../../../javascript/jquery-atwho/jquery.atwho.js/https://192.168.6.10/assets/webpack/common.bundle.js:19235:1
../../../../javascript/jquery-atwho/jquery.atwho.js/<   
https://192.168.6.10/assets/webpack/common.bundle.js:19149:2
../../../../javascript/jquery-atwho/jquery.atwho.js 
https://192.168.6.10/assets/webpack/common.bundle.js:18608:29
__webpack_require__ 
https://192.168.6.10/assets/webpack/webpack_runtime.bundle.js:55:12
./commons/jquery.js 
https://192.168.6.10/assets/webpack/common.bundle.js:21974:78
__webpack_require__ 
https://192.168.6.10/assets/webpack/webpack_runtime.bundle.js:55:12
./commons/index.js  
https://192.168.6.10/assets/webpack/common.bundle.js:21953:66
__webpack_require__ 
https://192.168.6.10/assets/webpack/webpack_runtime.bundle.js:55:12
webpackJsonpCallback
https://192.168.6.10/assets/webpack/webpack_runtime.bundle.js:26:23


and

TypeError: __WEBPACK_IMPORTED_MODULE_0_document_register_element___default(...) 
is not a function [Zjistit více] main.bundle.js:10029:1
./behaviors/gl_emoji.js
https://192.168.6.10/assets/webpack/main.bundle.js:10029:1
__webpack_require__
https://192.168.6.10/assets/webpack/webpack_runtime.bundle.js:55:12
./behaviors/index.js   
https://192.168.6.10/assets/webpack/main.bundle.js:10089:68
__webpack_require__
https://192.168.6.10/assets/webpack/webpack_runtime.bundle.js:55:12
./main.js/<
https://192.168.6.10/assets/webpack/main.bundle.js:22926:71
./main.js  
https://192.168.6.10/assets/webpack/main.bundle.js:22886:29
__webpack_require__
https://192.168.6.10/assets/webpack/webpack_runtime.bundle.js:55:12
webpackJsonpCallback   
https://192.168.6.10/assets/webpack/webpack_runtime.bundle.js:26:23


I also tried to regenerate webapack and assets. It finishes without errors 
(after instaling node modules indexof and randomfill)

I also tried generate assets using yarn and
# bundle exec rake gitlab:assets:compile

but it does not finish successfuly, complains about missing 
webpack-stats-plugin, which seems to be installed.

Any clues what can be done?
This all bundler and node and webpack and etc. magic is ... (+ i have to allow 
traffic to our protected network, for npm to work)

Thanks,

Libor


- -- System Information:
Debian Release: buster/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-rc8-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlqC+vgVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOBMwP/3Xk/cZcsEQf2S99vDtAZRv9Rdwl
IkYQr2NN0Mtq/xMetF8eDEugMOA2O7QoRMYV2iBuJ3Ork1oqPrrevtqonNltqIJh
UZZKy+SBQgYz8RLiGiZrvzKd82pBXjM8rHdMkH1EYES02MR09PEdvzdOyzvoHyQj
NvP6Y5dmYyZ7KEHDaDDJs3gObr/fs+yAoFsygB+aZObSyfYsiczyfVXQWgWg3GMb
v4g9ZSTUyoYOD1w/6xMSpShe8r3rqzr+st+gcR61VacC0ZREM2bA5M6Nm++b4e2E
XEE98rRC4YAYBBtYp0AIyVBSUM/vgR9EOGXsf9MuFUkUX1oT2zc2WJVSJzhi6Cv6
C3N1qQ9zRypDnSlDUyShJDaVvBbotejzpDtEN6GIwV/a+5yyl/iWq2id4fXSDqYH
jnE5iFOIv15jTQtYNBz6NGBwyKluRjbVPVAlADlQpEuKQpd7O2FyAWvSXN4axk74
6MLHIW2j6qDq5e3h4WrDMIhGvsbzVg826NdW27SUnxCCwUz4R/BGq1wGgMCgrxjj
OGx8I7hSZ4z9eBLyW7kU3KTHUY8YBd73716o8i8otS9rPecS40VfSNhUxRfivZSj
W/CboHerla+RQP/gIKfzzyad5Gh/ye6z8xZIcEH9AvcDr20vpev/FhhHY+Tbrrnd
JHwqhiFcTfmRtSmt
=9ewv
-END PGP SIGNATURE-

Bug#880195: additional info for bug

[Libor Klepáč]

Hi,
i can confirm, that with module from jessie, WS proxy works for us too 
(without changing my configuration sent in initial bug report).

Thanks for tip

Libor


> Dear Maintainer,
> 
> 
> 
> I've the same problem to proxy the Proxmox weg gui. My configuration is:
> 
> 
> 
>  SSLProxyEngine on
>   ProxyRequests off
>   
> ProxyPass https://127.0.0.1:8006/ flushpackets=On connectiontimeout=300 
timeout=300
> ProxyPassReverse ${DESTINATION}
>   
>   ProxyTimeout 600
> 

Bug#880195: apache2: Trying to use ws:// in proxy results in "No protocol handler was valid for the URL /ws .... "

[Libor Klepáč]

Hi,
just tried it on Sid with apache2 2.4.29-1, it shows same error

With regards,
Libor

Bug#880195: apache2: Trying to use ws:// in proxy results in "No protocol handler was valid for the URL /ws .... "

[Libor Klepáč]

Package: apache2
Version: 2.4.25-3+deb9u3
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

i'm trying to enable websocket proxy for customer on web server running Stretch.

After enabling module
# a2enmod proxy_wstunnel 
Considering dependency proxy for proxy_wstunnel:
Module proxy already enabled
Enabling module proxy_wstunnel.
To activate the new configuration, you need to run:
  systemctl restart apache2

and restarting apache, i try to use this snippet in vhost configuration

ProxyPass "/ws" "ws://127.0.0.1:9000/"
ProxyPassReverse "/ws" "ws://127.0.0.1:9000/"
ProxyPass "/wss" "ws://127.0.0.1:9000/"
ProxyPassReverse "/wss" "ws://127.0.0.1:9000/"


it ends with internal server error and log says
 AH01144: No protocol handler was valid for the URL /ws. If you are using a DSO 
version of mod_proxy, make sure the proxy submodules are included in the 
configuration using LoadModule.

Acording to
# apache2ctl -M | grep proxy
 proxy_module (shared)
 proxy_http_module (shared)
 proxy_wstunnel_module (shared)

all modules are loaded.

This apache runs MPM prefork+itk, I also tried on another host, running same 
version but with MPM event, to eliminate influence of itk (I know, it cannot be 
run with mod_http2 for example), with same result.

Don't know, what to test next

With regards,
Libor 

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAln3LiAVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eO8dYP/0yAJD0qdpJsxsgNA2XPsNRIJV0x
eNtppVBVkNH29Nvapa+Cq1RheU79rNJhcUHldOb1iNz0u06G0OzmAuRrDk9tR5b8
yoVtb2N8EDYuyFmr4Nw1MhMVBgNf1tNXIfmMBLF3Ol0DysvtpEQeZMDpm9bkStfg
oWbq/YLECDNy9xT0IH+Mt8VoD4EiPSHFjB46iZ0Lvjj/ftsG0rJMUayyzCZ/s4Us
lGy6JYuMtdF53wZuGGFZTt935TblhUfWTEOypeJ/Sm56Zucnd6TXQBGeqh5F1WKk
Sn9G6w4KSyZNLZb93gkDJVrRBbLZe7HV6IktmIB5egj0k5o5DgnbG+IEr5vqPbid
7ZbTZz4w5UGJ/y3RC1MDjrTz0wX6taw3TocBQJpq1Ov0VZ9UkSjq3lNgL+oSwV0m
yWChI2ZNOrx8FTdQJXL7Ok7Yw4e6fYySgcyl7ahg+RUEZqDAvU5xxvVP74cFYWxB
uIzXZtKLBKI5X0HIDAXJ+pYmkCIxuHfBxKFKP2PE/CMw2C0UI+RM838t07tyUfnE
gV2e9KIG/WOTvGsUiRnmSN6020sE5MzyUSXmLmIeTkZoFpI5E3DXfkijN1nau4kA
2b3NymnfvqXx/eSd2Iu2zAQAApR7PoNmLwPaZYlYryY7hQqNk45YscQKnq91xM45
MLYYponhG9jT/W1p
=GrvM
-END PGP SIGNATURE-

Bug#863334: rsync: "ABORTING due to invalid path from sender" after upgrade from jessie to stretch

[Libor Klepáč]

Package: rsync
Version: 3.1.2-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
we had two jessie servers, main server and backup.
Backup was upgraded to stretch.

We use this script to transfer changed/deleted files:
#rsync -avH --inplace --delete-missing-args --files-from=/tmp/transferfile 
/path/to/data/ archiver@1ip:/path/to/data/

The file /tmp/transferfile 
is generated by app, every change or deletion of file generates new line.
App also deletes empty dirs (if deleting a file produces empty dir)

After ugrade to stretch rsync there is a problem:
- --
rsync: [sender] write error: Broken pipe (32)
ABORTING due to invalid path from sender: path/inside/data/dir/file.txt
rsync error: protocol incompatibility (code 2) at generator.c(1271) 
[generator=3.1.2]
- --
(because path/inside/data/dir was deleted by app on sender side)

Reverting to jessie version=3.1.1-3 of rsync fixes problem.

It was probably reported here (with patch):
https://bugzilla.samba.org/show_bug.cgi?id=12569

Can you please patch it for stretch?


Thanks,
Libor


- -- System Information:
Debian Release: 9.0
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rsync depends on:
ii  base-files   9.9
ii  init-system-helpers  1.48
ii  libacl1  2.2.52-3+b1
ii  libattr1 1:2.4.47-2+b2
ii  libc62.24-10
ii  libpopt0 1.16-10+b2
ii  lsb-base 9.20161125

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client  1:7.5p1-3
ii  openssh-server  1:7.5p1-3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlkm7d4VHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOhm0P/3BffHvVkTrmsunnZ+P84WGX7KOZ
gmZIaYYxDmgWmivCwW22w8ECpB2HPADBBYKJV3wHHFVKfuRdlQwl7b5N7bILmFcP
UasNqfRgs3nN/5+AcxuorNRR+nm3t+n28wMVIwQiqCFlmt0xgc+3ZKGYK/MZmiKm
16doXdAst+yS15PXVk/bRP7e0O3JBEzKok6DQc/D141ChexOEN768BahSFJtWSGV
1jnEa9DZzk49HoXAn9UTLYgH1Gy8NL+Lh4gthR3OQb85HJfzjlzsqFxjmu5bWx2X
OoVtegJn3d7u33CHPfhDPnrRzxkgMEEcHmCgz6XNRUN08jRVeHjl6lCwuck4pqaY
EtirqWMaA7fWgZFvAEXMKd6oYyhnYt3zCsOpABqL0TL5iztTsWSC/gfC1h/oL+ou
qYCCPtVrxsGm4tkuqgfBRbu/rgEwleI3lK+oV8YFguB7uW2meHFKoOYHueXBWSw2
rXC8Jnrhh/dlEj7CGKJbmvzZJCe+31vxXVzZMMXECd1zGA369RnT6RojO0f95jcE
XN0sqTJXnUopdFUSTQNuLttdSdOu1MXDFG4sc23F5lcca5fY0CBYcZSHAMqCydZb
QnIh9SKHQV+smnvaTQR79Rsg7bkl3nvQ65gob6jH6FZx9z/hEWdSSJSmIwIGuXVc
ozE8H8uHcJSUlIck
=Fry9
-END PGP SIGNATURE-

Bug#862240: munin-plugins-core: mysql_ plugin compatibility with MariaDB

[Libor Klepáč]

Package: munin-plugins-core
Version: 2.0.33-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
without patching, mysql_ plugin doesn't work with MariaDB.
Attached one-line change, please consider it for stretch.

before
# munin-run mysql_commands 
Unknown section: INDIVIDUAL BUFFER POOL INFO at 
/etc/munin/plugins/mysql_commands line 1099.

after
#munin-run mysql_commands 
Com_delete.value 0
Com_insert.value 1
Com_insert_select.value 0
Com_load.value 0
Com_replace.value 0
Com_replace_select.value 0
Com_select.value 340366
Com_update.value 1681
Com_update_multi.value 0

This change is part of
https://github.com/munin-monitoring/munin/pull/109/

which got merged to 2.1.* series, it fixes some more compatibility, maybe it's 
worth using it

Thanks,
Libor

- -- System Information:
Debian Release: 9.0
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlkSvq4VHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eONOoQAJsCKG7RlVD9ssl5KsXbbjW4puO8
qQorYdR9CZi2cBJPnOHe2gJocOZtSHPeER1bOrYiH3S/PGk5Em7643vk4EeLuQbv
XpINyQTFB1s4IkOFWpIKVtbolu0MCxdDWviv2gr9ZPHZBNJlCFfFKbza0Vhi8/Z6
llRB7ZyjQqqh7cFqeMcX6DgCgw91ABpDvqfWQScqjwVjrItIWY9zRtdbgMLsKHGc
5PK4ml1vcYBCds8cU3fVvXVJ+6tZpet9QxbQjoXCHhOq56KtakZs6Pe9wZGLg+PU
JM/wb/GrnenZ8vd4weThgRvV1Jy4FHDP08q9c2HIKX7YHu34qWhN5nN+Scs5YXmi
qZwMnsGhUYCS0uF4nUcm8QmbcX4F9sZE+A7GvR3meLFa3qsdn3a1bxgmfUIGEYIl
2OfM4P57PEaT1gKfedJkvmXTfeswd/tg5jRvLTJ1SD0W6xz2vi3J97OqmEH4L0k1
Xu3pa/sbFcwFqVRaFf4MxCwPdax18wD/9Miq/hVhmgK69k3kjEZxoMmUh4G9kEhk
VJ39+5Z3+a8ZZwFCrBxQ9xZFiTEgK3DfKrNl0rJlIL953vzzKurvy0fMl5OvonFr
4CBAcXQxQVt6XOyMGwo2RUH1RTu0xwfkdjS5R5xnFNAPQxpUirnaR0Zn/W+a3ryJ
cxli/Z6WMyGYUOHL
=bj+Y
-END PGP SIGNATURE-
diff -ur a/usr/share/munin/plugins/mysql_ b/usr/share/munin/plugins/mysql_
--- a/usr/share/munin/plugins/mysql_2017-03-03 23:44:00.0 +0100
+++ b/usr/share/munin/plugins/mysql_2017-05-10 09:06:44.0 +0200
@@ -1072,6 +1072,7 @@
 my %section_map = (
 
'BUFFER POOL AND MEMORY'   => \_buffer_pool_and_memory,
+   'INDIVIDUAL BUFFER POOL INFO' => \,
'FILE I/O' => \_file_io,
'INSERT BUFFER AND ADAPTIVE HASH INDEX'
=> \_insert_buffer_and_adaptive_hash_index,

Bug#862238: munin-node: Mariadb authentication change

[Libor Klepáč]

Package: munin-node
Version: 2.0.33-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
on new installations, mariadb changed way of authenticating administration 
account.
There is no debian-sys-maint account, root is authorized by ... being root (by 
logging in).

So, attached patch fixes mysql plugins authentication.

If you upgrade from jessie, debian-sys-maint is preserved (I guess?), 
but change in this configuration file is covered by conffile, so it is ok,  
right?

Only problem should be, when you ugprade from jessie (with no munin) and 
install munin later.


Libor


- -- System Information:
Debian Release: 9.0
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.11.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlkSu3UVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eObq4QAJo8dzQ0aPkAclyKrclwjaw2+p0T
8Cdc1VEn05DeKeeQdFct+FMVGsW+U23OGx/1TFn9e42WbZfU08J6y6QevR/+CtYK
heVzFde6jEK4u823prgWuA9coBU8MteC7QgD3wm+OFAeOkDLumiyfAfmp25hSB7E
Y9Z/oLs4UMQLbjtw5oSMbByzSvIo1Qncy9e+RKtJ6rYgyBzjqwbUq5dFTskV57ri
bgYWdbcv+oq88y/+v7Ir+4buE6xMGKVE8cqViE9op8OwfVNwAyeLJ/ZybyhsQwPa
V57k8qDafn9mWrdFVl9zYgclIOMhWAKmB6AqWpqffMFTAS48Qfc2RkMCPqNp20T0
Yr9S5aADX4rwypieEz6roSrIcYCXqRC4drUKI0R04kLraLu2Jbu4G/V7iqCoDBs/
Lp5Plt5BveHe4EsLxMYEKUcLr9EpenVztUUfIWXMBH0jlRw4O9g/pPbyC0KncLRm
3xdvV+n9T/aaT5KERu40VBkV9v/RLfTBxAW1p2KVyo4BcP7+YN910ENNU2xzupUY
Ujm2s/txn4u9KV9FLnPxglrUICe4x81lO1hpXw/GlAxWLSdvb631EMM8cizo1Z2+
WWOH+dY7OVpbHZZPmKBSIZIPhgQIi2jSzVwMMXKEsTYK0JSrbYJRlQtni2h5v/19
ulgb8QRIPtPbaipw
=Y7ta
-END PGP SIGNATURE-
diff -ur a/etc/munin/plugin-conf.d/munin-node 
b/etc/munin/plugin-conf.d/munin-node
--- a/etc/munin/plugin-conf.d/munin-node2017-03-03 23:44:00.0 
+0100
+++ b/etc/munin/plugin-conf.d/munin-node2017-05-10 01:06:27.0 
+0200
@@ -73,7 +73,7 @@
 [mysql*]
 user root
 env.mysqlopts --defaults-file=/etc/mysql/debian.cnf
-env.mysqluser debian-sys-maint
+env.mysqluser root
 env.mysqlconnection 
DBI:mysql:mysql;mysql_read_default_file=/etc/mysql/debian.cnf
 
 [postfix_mailqueue]

Bug#852787: gitlab: Doesn't restart services properly on OOM kill

[Libor Klepáč]

Package: gitlab
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
we have low mem instance of gitlab - it used to have 2GB of ram, now it has 3GB.
Sometimes, it runs out of memory. (usually at 22:xx )
OOM killer usually kills one of sidekiq children.
It triggers restart of sidekiq, but also of other gitlab services.
But gitlab-sidekiq is the only one, which is started, other are left dead.

Can this be somehow addressed in systemd service dependecies?


Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAliLGIQVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOcGgP/3eJAMqQoBWxG48YXLnfx1D6YZ6h
K4CLe0fpz8rFG87v4qsfyszA5WF3qY3QTffYKXxDJq5Z9QAaV2V+k5Jn0j0Sqhes
IsZqN5g4XvOdyYB6UEy6IGdDhiogiqCeHTz/gRL83WYDb2c+aIykZVYUWSS2MELl
fIpDyIn5FvlRs42VQu0u6x/Wi6b1+j55Y7KWo3j/bET+8MQzg5fOEdIO3qXGTGrf
A5wM0QQtFsOmcvQNWz7hWn7Lm4Fd5Q5U48O0MRiaJNTOUA/OOfoHgRBwHcBAUtvR
2alVQwb9FlH90wdRhUHARJEX10m2+duTvRw4KrP2PHaFcy5l/GJiVp8RV5NrAkHF
Fo9xDrmNjDnCAhjT54gOaudAYW5P9MpqJDHOtcaenvsoK8OHaEFh85kBxYhDj4DA
T8f7qnoHzBsHXzDr3zLMas8TGVfWRc/H7HhhL19WTDwCyXJfm+NBcwYd5RUXysl/
TdZE9K09uhxKtMNbnhAqfPk08XTmTRLObRGx/2U8wWaU8f3X1aZOJLANOQUKuq2Q
57eEIQ3Ed8eY8AUN95jfxq5s9QbgLhwGf8hl6eyzXKrAtHxq/coeN2rNzdaEYIac
A7VRgk4id1qnwqdAFgy6DoNTzqK2vcAjy5Ix+DmoFPHmaxqIuXj6O9pNr5+/9lL4
/0DxTlrb5zieOvBi
=h2TC
-END PGP SIGNATURE-
Jan 26 22:15:18 gitlab kernel: kworker/0:0 invoked oom-killer: 
gfp_mask=0x24200c2(GFP_HIGHUSER), order=0, oom_score_adj=0
Jan 26 22:15:18 gitlab kernel: kworker/0:0 cpuset=/ mems_allowed=0
Jan 26 22:15:18 gitlab kernel: CPU: 0 PID: 9360 Comm: kworker/0:0 Not tainted 
4.8.0-2-amd64 #1 Debian 4.8.15-2
Jan 26 22:15:18 gitlab kernel: Hardware name: VMware, Inc. VMware Virtual 
Platform/440BX Desktop Reference Platform, BIOS 6.00 04/14/2014
Jan 26 22:15:18 gitlab kernel: Workqueue: events_freezable vmballoon_work 
[vmw_balloon]
Jan 26 22:15:18 gitlab kernel:  0286 1c838855 
8831f925 972ef1ab3d08
Jan 26 22:15:18 gitlab kernel:  972f38b02080 881f7491 
0206 8818f2e9
Jan 26 22:15:18 gitlab kernel:  972f3fffccc0 000c0246 
972f2d66c080 972f38b02080
Jan 26 22:15:18 gitlab kernel: Call Trace:
Jan 26 22:15:18 gitlab kernel:  [] ? dump_stack+0x5c/0x77
Jan 26 22:15:18 gitlab kernel:  [] ? dump_header+0x59/0x1dc
Jan 26 22:15:18 gitlab kernel:  [] ? 
do_try_to_free_pages+0x269/0x350
Jan 26 22:15:18 gitlab kernel:  [] ? 
oom_kill_process+0x222/0x3e0
Jan 26 22:15:18 gitlab kernel:  [] ? out_of_memory+0x35c/0x3f0
Jan 26 22:15:18 gitlab kernel:  [] ? 
__alloc_pages_nodemask+0xd67/0xda0
Jan 26 22:15:18 gitlab kernel:  [] ? update_curr+0xe1/0x160
Jan 26 22:15:18 gitlab kernel:  [] ? 
alloc_pages_current+0x91/0x140
Jan 26 22:15:18 gitlab kernel:  [] ? 
vmballoon_work+0x47f/0x704 [vmw_balloon]
Jan 26 22:15:18 gitlab kernel:  [] ? 
process_one_work+0x160/0x410
Jan 26 22:15:18 gitlab kernel:  [] ? worker_thread+0x4d/0x480
Jan 26 22:15:18 gitlab kernel:  [] ? 
process_one_work+0x410/0x410
Jan 26 22:15:18 gitlab kernel:  [] ? kthread+0xcd/0xf0
Jan 26 22:15:18 gitlab kernel:  [] ? ret_from_fork+0x1f/0x40
Jan 26 22:15:18 gitlab kernel:  [] ? 
kthread_create_on_node+0x190/0x190
Jan 26 22:15:18 gitlab kernel: Mem-Info:
Jan 26 22:15:18 gitlab kernel: active_anon:98986 inactive_anon:102318 
isolated_anon:0
   active_file:23 inactive_file:47 
isolated_file:0
   unevictable:0 dirty:0 writeback:0 unstable:0
   slab_reclaimable:3358 slab_unreclaimable:9520
   mapped:1580 shmem:1984 pagetables:3919 
bounce:0
   free:14226 free_pcp:30 free_cma:0
Jan 26 22:15:18 gitlab kernel: Node 0 active_anon:395944kB 
inactive_anon:409272kB active_file:92kB inactive_file:188kB unevictable:0kB 
isolated(anon):0kB isolated(file):0kB mapped:6320kB dirty:0kB writeback:0kB 
shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 7936kB 
writeback_tmp:0kB unstable:0kB pages_scanned:0 all_unreclaimable? no
Jan 26 22:15:18 gitlab kernel: Node 0 DMA free:12136kB min:232kB low:288kB 
high:344kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB 
unevictable:0kB writepending:0kB present:15992kB managed:15908kB mlocked:0kB 
slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB 
bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Jan 26 22:15:18 gitlab kernel: lowmem_reserve[]: 0 2976 2976 2976 2976
Jan 26 22:15:18 gitlab kernel: Node 0 DMA32 free:44768kB min:44820kB 
low:56024kB high:67228kB active_anon:395944kB inactive_anon:409272kB 
active_file:92kB inactive_file:188kB unevictable:0kB writepending:0kB 
present:3129280kB managed:3068696kB mlocked:0kB slab_reclaimable:13432kB 
slab_unreclaimable:38080kB kernel_stack:3648kB pagetables:15676kB bounce:0kB 
free_pcp:120kB local_pcp:120kB free_cma:0kB
Jan 26 22:15:18 gitlab kernel: lowmem_reserve[]: 0 0 0 0 0
Jan 26 

Bug#851648: gitlab-workhorse not logging to file on systemd

[Libor Klepáč]

Without this patch, you can still get logs using
#journalctl -u gitlab-workhorse.service  -f

but it's not consistent with rest of services

Libor

Bug#851648: gitlab-workhorse not logging to file on systemd

[Libor Klepáč]

Package: gitlab
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
just a little patch to enable logging of gitlab-workhorse on systemd.

Don't know, if it's useful, use it if you like it, drop if not.
Personaly i don't like the /bin/sh "hack"

Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlh94pwVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOD4wP/0NTNHL79ykF6zgtQ7Iw9YQJqC9/
8FjaKM9Vr8l/9sfniBo9WLKFdTwMFy74YlFhcX1501qj0Vr+5k487PcYg3hzWKdt
Phgi+WOs1Ca88vew6eVhLTfJrkVU4AJkweobLpccOVIvLDkk7+Qqaoq7myGIeYVy
UKoPDqq41bBbwDWZVQ6t6C6fqFY5+bL4ZG221xFlpktE6xWKQhoSOI4z/g1Gq0Wn
lUEdibrhWll8dg9BSwi3zdXAbsGe1dtWBuTenqaNMk9ey/GI4TaqY1T4w619a9L/
XAwivqPClEjkHl3/2qm1vWpEQmrR98WAA+FxAc0CjoQVyhuWwId8RJJsfXGzjXCj
GTp6HsnLsAiSHsNV2lWnrN677wd0tRH9SCl836mpxZYkgJPTq8wPF8ovgZfzizsm
OX5Y0/NQymNJT+fcESXcvny033sVMrEeTi1NOrw1d4bLKGvmIyJ5OKj3u/JaGLm9
6MfiCbnYLbB1DlJqm/b+HCS6fygcigWHi4xYA03IrXglc1il05h7AO52XVDhTKjZ
bVrXFy4lATxXXeSRqzDy/pWHZ0ZykeREdYwcl+Rp01YvzQgfmajzgwDQkuzfHuu3
Q/IMjVnmDbbJX7LgaYECtmPRAvejHvMOj6ndvdCBHtjc1EZZ+ezwt7NKpLwbdSpj
ckaM8ios8+p9u+QB
=h3uq
-END PGP SIGNATURE-
diff -ur a/debian/gitlab.gitlab-workhorse.service 
b/debian/gitlab.gitlab-workhorse.service
--- a/debian/gitlab.gitlab-workhorse.service2016-07-19 11:11:39.0 
+0200
+++ b/debian/gitlab.gitlab-workhorse.service2017-01-17 10:18:52.816505949 
+0100
@@ -13,14 +13,16 @@
 WorkingDirectory=/usr/share/gitlab
 EnvironmentFile=/etc/gitlab/gitlab-debian.conf
 SyslogIdentifier=gitlab-workhorse
-ExecStart=/usr/bin/gitlab-workhorse \
+ExecStart=/bin/sh -c '/usr/bin/gitlab-workhorse \
 -listenUmask 0 \
 -listenNetwork unix \
 -listenAddr ${gitlab_pid_path}/gitlab-workhorse.socket \
 -authBackend http://127.0.0.1:8080 \
 -authSocket ${gitlab_pid_path}/gitlab.socket \
--documentRoot ${gitlab_app_root}/public
+-documentRoot ${gitlab_app_root}/public \
+>> ${gitlab_log_dir}/gitlab-workhorse.log 2>&1'
 Restart=on-abnormal
+KillMode=control-group
 
 [Install]
 WantedBy=gitlab.target

Bug#839702: gitlab: logrotate not working?

[Libor Klepáč]

Hi,
is it supposed to logrotate logs on it's own?

If not, then i think , that file 
lib/support/logrotate/gitlab
from sources should be adapted for debian paths and 
installed to /etc/logrotate.d

Libor

Bug#851570: gitlab: git operations over web causes 502 error

[Libor Klepáč]

Ha, nailed it

we have
worker_processes 1

in /etc/gitlab/unicorn.rb
because of memory constrains

When I increase it to 2, it starts to work.

By the way, gitlab-workhorse is not logging to file, when started over 
systemd, i have to use journalctl to find

Jan 16 15:08:10 gitlab gitlab-workhorse[10049]: 2017/01/16 15:08:10 error: 
POST "/packages-bcom-lib/bcom-lib-cronbuster/create/master": badgateway: 
failed after 61.287s: EOF

for futher searching

Libor

Bug#851570: gitlab: git operations over web causes 502 error

[Libor Klepáč]

Package: gitlab
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
we have problem with git operations over web interface, all leads to error 502.

I have just upgraded two instances of gitlab to 8.13.6+dfsg2-2, our from 8.10.x 
, customers from 8.9.x.
Before update, git operations did not work either

I don't know, how to debug, production.log doesn't contain any error.

We have gitlab on apache not on nginx on both instantions

Any clue?

Libor

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEPGZVVU37tFmB0TQv8O+MbsKfR44FAlh8uWcVHGxpYm9yLmts
ZXBhY0BiY29tLmN6AAoJEPDvjG7Cn0eOaJAP/2jcw4A04X2gERyFNKRKxkUbfOni
KJlt9wHMwIlJzv2Jmcf9fbHUEMUe4Ug4DT3AG0e6hMoPThK9AuUIdUrDff1W1GZh
8xr52TRcKq3izcv+n9ou8djuvtL5L3UoDIXFN+e7z14kDb09eypnEwmagr+siKPh
+/ohXuVvszW4nY1DMWd2cBXxIhMOP20tKykqls6zqX6MpFTGqrpsve4h3JbRXdYs
ksn6Vs4JfLu7uuQBSA8hjX3ZLsCJhYx1/A78/imWT/1X+JDy1bT97oJ9YqIgV5dQ
1zqvEdFVnnLHczCvMBSu00Tgwv0A5yBzD60PPAqDv5dUB+kLJEsaeEt3Xq3dAYrv
NwKEPdz0vDIgpuKXBlL5xyFfII7OkB0E8udd1GMDt3ik4be7eB3pJkR0Dt9XENNH
/hhhVJxnOwxyMc8AX4ombpPgNBpwYwxJ+021WQLnbwhxJbyRssIbuegSNfNPDygw
jz/OMH9pk0E2F9TQ2vQEBRSDodjyaEXdfib0RGZFXmRj/V4E9JsxForllSY05pV7
9FIZCMoRiV6v9gsSiJiLOuv2tQuZGkV6wsy19t5LDDxXPgj/cIiDDEX79mIa98m4
0YiReNGSP3EI2wZP7dU9h+kjzKM9Y18JRVX1sm6/Y6BuksISULWoFY5mlw1OiP3r
RzcWMq8NcR1+9u6O
=SDwH
-END PGP SIGNATURE-

Bug#826931: gitlab: page with diffs (commits) - error 500

[Libor Klepáč]

Package: gitlab
Followup-For: Bug #826931

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
i had to upgrade ruby-gitlab-git to 10.1.2, because gitlab needs method 
"tag_exists".
You cannot push commits with tags without it.

So upstream Gemfile is totally wrong expecting version 10.0

Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXYVLNAAoJEPDvjG7Cn0eOL7EP/1EC2CcZrhfubtEMaqQ1NLnL
eVmHSan4qJ6GzhhuIKsrDlPzoGzAkgDSIA9E8Lskp4HRPNLVGu1LwfT8VH6LDRsK
O/JOkHXMihukG8EHILknTTCmrW99laCMDeIxMELRdudbgCXNooRo69TROV4kZ3UQ
y3wzdy41ey/aOvRGxgqU3Z2HugasbQYw4fjuxFktuz6e/GCVpCsMHYXRU59zTQEA
N0jWlrQ+NRGtMHPH/SUMyc0UVSkPa9FqXVa3WmOKa4wXHzY3UV5/UpLwwPeyuAY5
IcqwWeB3IXJi2lqEqq/tU+PbW2uDrJlkyJ75467Nnyu4ScswA35KQa1RyvbxFL7y
kEdmtCC+s4kjd4zLV3ttE1AqYFxLHLuvGemgMYKnOVkStlt+bvr/OWJd7CwMx0e5
dwYJIj9gVNh/93uWYhYliRYQoxY/CWCN2mmg8ZM/rj8FDh/Oxv3TrXyRrF0Ym69V
jAp4MTTcHreC5k+/hu7KlW6WwKMK3fl79Xk4kWUKxVx/co8MprnQJZ7+j7PEolNh
ZPXW9LQ1OpaoLMBngmUvHbKqMmNJG5gbxk79xF+RfEmuUdKvk9JghgmPD2MzEoYD
POuqipSO6omLvwkuJanV2YU+4EVyC09hXgEu45myJz4ZiY9UZh8FB1LyuRa8Esp3
S1HpMe1M/4RX02/QFma5
=JOzJ
-END PGP SIGNATURE-

Bug#827163: gitlab requires gitlab-workhorse at version 0.7.1

[Libor Klepáč]

Package: gitlab
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
please tighten dependency on and update workhorse, gitlab doesn't work with 
0.6.3 in archive.

Thanks,

Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXXmmPAAoJEPDvjG7Cn0eOgjsP/2Cd3jN/APwfSauDr9SuqrE5
ImpSVD/WgBYg6rmKiQIExkD3udfHxVBZv96qxWeEAEWmJtempcUqjKmg6CioCitT
De7s04HJZQrcDISH2V4p4zaWSL/7Rw2Yfi2nLFeSOqvFkultQ68y/kdn+snb1DGr
BkiUyxkLayE7w0LOmtgTqz8pLzFdEgsaLKEpjX+ihim+Rg1TYn72gCxqb3xf8AAA
rhdFKAdQ9zd0yk3gUt15cvmxMoPU6Wm/oQRltk1Ep9OsT0QWnA9Vd+1pX1Gu+xJv
PXMwKBeuJquLDg2fUgA2NTWK0rTy1wp+BIm3Ym4sPtPDrEtV6ZiCGunD9mlzfFvu
cfatBMVnGI9u7h5jD2UzBa1TMwfNbtlSkYE6cuRhZmMJQUKspkRbdk2zLEe63m6v
nxLhOCDV82/EN3Be+syjhoWc8NlJJ7titWKOGYiGKx+yDABngvLz0UrC4aHP7Ano
lSPY751wkpKT4n6q0qeDvJL13PzmywbQtcmwE/evidf1sZFQG+Hb9+7dGUB63l1C
mshQBSiDptNBAit1rgLN0pspyCn+q4tBpKJprmlpK6XZBXfLXZPIagadKAh/v+Ca
s5AXkHMoq7MetphR043xhI1JKtDBaVAP0PByyhVCzUXuZDsEgvXmsUnJc4a5ScUW
5NLYNEOR6OezVZR1uJLq
=dKM3
-END PGP SIGNATURE-

Bug#826931: gitlab: page with diffs (commits) - error 500

[Libor Klepáč]

Package: gitlab
Followup-For: Bug #826931

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello, 
i have manually replaced ruby-gitlab-git files with version 10.0.1 and it fixes 
this problem

Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXWm62AAoJEPDvjG7Cn0eO1tAP/1qy2oSMEEmvSkFRjJHDCU9g
0yWvQC4xKjcM0y0xIYotnv82G7dxJNsNU1oC4zOhTymty7hj4MtbGZDEe9olNuhR
nWgxHU0FNcCrv+io1V1WaK9I0S8TQlHkYlZaCSfjdCz9nAMCgU9e9c8jTfiyDvDB
Alq6SmeaqQwygjTZCeTQCx/jM4yaapHj8Vtnc0TaE8m2xjAASK5DkF3wFFHvS7T3
xPvhpqgbFkxtDCPfXh22R8oNs2EjVij4Y4NW5sBxVPcntzfATZO963jL7zy+0306
neC5LBlMW21YCw9Xrc1527YtfWPHLSttilowTcQZYkYHSKLUvXOEe5Pa7Mxxb3lI
dWH3Iou0EmcMIvR/9NDy3Omvn03LJW88ZCfJGxAjvHjHzZb+R6SfFaERkcSt6B5d
PYRNBujcVV33r7xfn69oWWgLkf4FHPyV6uADop+OX+B0Cw2Nx7ZtGdTmclQzaGHC
RdW7ypXCWxqPe/ZfPZzfKuCVlATFycwq8Z52vc7c2wEJ7xus8ioQrM7o/Fg/v0hK
gTJM//bunpflEN8YO4oEXJ/WHz6JyH6XFpOBopwO7BgZ1Lse/oig+iyqrt5Zhox/
mDNIvGLI8fXO3Cxaj2UVzwe6qtDZs35NvieLrlKX6tuY8qCVIk3N28yvPcnAW0TY
9hzTXyxz5J9Ki/3VRDP0
=+1tP
-END PGP SIGNATURE-

Bug#826931: gitlab: page with diffs (commits) - error 500

[Libor Klepáč]

Package: gitlab
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
thanks for packing 8.8.2 gitlab.

We have upgraded yesterday and have problem with commits pages
- -
Started GET "/group/project/commit/xx53b0d3b0d0d87cf6f478b150ce689b8151a1b6" 
for 127.0.0.1 at 2016-06-10 08:25:33 +0200
Processing by Projects::CommitController#show as HTML
  Parameters: {"namespace_id"=>"group", "project_id"=>"project", 
"id"=>"xx53b0d3b0d0d87cf6f478b150ce689b8151a1b6"}
Completed 500 Internal Server Error in 343ms (ActiveRecord: 22.0ms)

ActionView::Template::Error (undefined method `diffable?' for 
#):
42: - return unless blob.respond_to?(:text?)
43: - if diff_file.too_large?
44:   .nothing-here-block This diff could not be displayed because it 
is too large.
45: - elsif blob_text_viewable?(blob) && 
!project.repository.diffable?(blob)
46:   .nothing-here-block This diff was suppressed by a .gitattributes 
entry.
47: - elsif blob_text_viewable?(blob)
48:   - if diff_view == 'parallel'
  app/models/repository.rb:439:in `method_missing'
  app/views/projects/diffs/_file.html.haml:45:in 
`_app_views_projects_diffs__file_html_haml__2130845417718406234_70613300'
  app/views/projects/diffs/_diffs.html.haml:28:in `block in 
_app_views_projects_diffs__diffs_html_haml__1571110138484770322_71701000'
  app/views/projects/diffs/_diffs.html.haml:23:in `each_with_index'
  app/views/projects/diffs/_diffs.html.haml:23:in 
`_app_views_projects_diffs__diffs_html_haml__1571110138484770322_71701000'
  app/views/projects/commit/show.html.haml:12:in 
`_app_views_projects_commit_show_html_haml___791189859704013076_79050720'
  app/controllers/projects/commit_controller.rb:30:in `show'
  lib/gitlab/middleware/go.rb:16:in `call'
- 

I seems, that it needs newer ruby-gitlab-git package.
This method is in master
https://gitlab.com/gitlab-org/gitlab_git/blob/master/lib/gitlab_git/repository.rb


Thanks,
Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXWmDrAAoJEPDvjG7Cn0eO7xYP/1GHdZuT10JJ/P9Xj2XotkGk
3vFzchr+Iq7B5Co/ldSGU88+L484/MP4fg7ZhcBAbx/mEZT7MzTl7gBfHnUf6qrl
InxmFVlwCkiC/p/dsdoHxjqvrpm8kK6hpbFtGvG7kCpxeD11LU57avFaOEnKRm3x
7G9jdLDSJTwTC+8MkYr+U/iK0QYaS8bWqgnyjk3wwjjRSpXbLjVXZbvprOXdvlvP
pofKmks9ZY4tLg0qBUfyVvSAK81yhcbD7FaoZ6w7QFu6avhYxg+ZQRBnokSgMyXl
KIYx+mWckmghDRrXdFEReo9oyDa6q5C1fH+H4cjLe8tCFfeAvnhNSOTqeFpTQCTr
/i+1WmPbKAdjeEiXsUjgxUm80l4GErRB6UTSSeyFtSxwEpmf6ekO3ZpD7xovuD0i
jy4HIyYX/HcDnSRlfOq4FnEFfTpJjrut/m1Vup4JhMOtIWQsK9Jqp5mju0tNRUZC
4bqOl+ETNTXP8raxWDZT01I70BpHjCXdBO/iGoDQ2NStyvWPaz46094ro9Nl3mBz
Nd5H7ivJt76braHgnb6Is8n1sssf0r7TvfzP26GNe12yKkgqk4PttCdisay7sQV4
FTR3rVsnoh9+S+ArKjzyqsHPukHnCO5aVzkxReAwYdsMNlhZ0dEumzHM/m0OuIu1
nkFJn+6+Jnbckr1QKBIZ
=ksvf
-END PGP SIGNATURE-

Bug#819903: gitlab: runners page not showing

[Libor Klepáč]

Package: gitlab
Followup-For: Bug #819903

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
still happening in 8.8.2-3

Libor


- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXWl/LAAoJEPDvjG7Cn0eO4dMQAKzCfIk0u64PXLz2Mct2ud8B
X8Zpio96tQYETGrssAFtN8hJb0koCZWeUFZemXSIULMHho2OiW1MRwZZnjDvH53b
jY+XHxRLHUFLY87EPnKzcntQPPzrUmIBr/MAWnrSNpdzvM0BfihEn+XninhUCsYg
ftelZhf6vAscFzbO4YU8fDyh5qaIqJtpsj0qj2m4ncsYC7virxYqTyUFK+v5pMD5
PAgVkiL9R2W/Bl+E4Wn2bjSLH21bVwayz/pil72FNKH5usVVpY0iEv3idX/Ti3je
loIo3OE1MMoLbKruSoYFDnkkAdvPilm95idZwApVXAG0djzRdjYtwdLSv1v4wUp0
FiRqJjsTRgTZSQm4xeq3s5d9pHcn+oZVtVRPNcf8YnMx+it3iDmLzjrUzAzvQr8V
wQt1/hwRA/QN+6vPXsE6r9QUixW9Q8NZhG7V6JFXHWNpOV4h7KgumxIGAfWEW+O4
aMIAFJS/lDEKCBgdS/yyMIspgjxAwIWm9o1RnBVMTa//3EQ/Emfhmp1iDs0174L7
29wzEg52JisD09zjQwfnx3SU0C+0xtV0hBgaWOdmEna+G4E1GZEJHsFh3I2ApNTu
CPd4305Byes2nn4SqswkCbcjw8P6ACz0w8Sdz8ePJsjvu3egQmgUyvb5MU187+rV
a4wCF9NpA9twmxlcFQmB
=2XP5
-END PGP SIGNATURE-

Bug#728660: libnet-smtp-tls-perl: Uses wrong syntax in SSL_version argument and warning about invalid SSL version

[Libor Klepáč]

Package: libnet-smtp-tls-perl
Version: 0.12-2
Followup-For: Bug #728660

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
fix is easy, just remove SSLv3 from SSL_version, it shouldn't be used anyway.
There is no need to remove SSL_verify like suggested in #728248

Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libnet-smtp-tls-perl depends on:
ii  libdigest-hmac-perl1.03+dfsg-1
ii  libio-socket-ssl-perl  2.025-1
ii  libnet-ssleay-perl 1.72-1+b2
ii  perl   5.22.1-9

libnet-smtp-tls-perl recommends no packages.

libnet-smtp-tls-perl suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXB25IAAoJEPDvjG7Cn0eO4lUP/0DlUJGL06LeqMxIT/QSEfRA
rNA+l3qtXwtq81UD0Uxaoa7xjwkQlPGh6+LS6vNtmlx2WnUodZ3Qyqnl+eY9x+pU
i/uxWlo77YCkHHX5Hu3nxn+RE3Av4rbPqYYk8M8D8w8lRc/j7mjxk4hTsY5qjT9Z
t1BowZJgtEs1lWEAX9SChDMD/ghDpn6Gu5/v4OlGIoMkNxZWGcDBjnruc9keGp+D
BB4h9FDz0DnHUnZbOhUBjdYGJhKNFQNN9DxuTdKrCh7tKU6V59cDOS0Ah9iOoB3W
FRqczkDTsThKCZNC2ZajMgN3DY+EKQkYC44RQmmhjbXoPlnxAm0kHy4V4iCBtXFS
kgm5IrTcbxwPHXTHCPXXdeaoeN9QmegGQ9prVJEDHcmAti922jRTzOfYv5c19IeX
9Gvtm92PhKuMOM+iWiJjvQ346THz26mW2UcauYcxrQMq/6loaNA6XtLAQBHhqtY+
Mywqw2YywIozeEhaxxuivTJdfIGjl3fVUMgxplUGO4HJZJ31jAxI1kGML1yhY2Jl
hSjtaOtmL5udoRx87vsoZm75RXY1bPkaOwHWyb0AM6ne40h5pd6ylLaF9ofeUXB9
CY5c3dSRKvjZasbctRA2r1dLMnIV6YOluh1zr0uvth0rJg+A28rfVUmq/1qWF939
REnzJhwMqGFUdKzPjLOm
=RTat
-END PGP SIGNATURE-
diff -ur a/TLS.pm b/TLS.pm
--- a/TLS.pm	2006-01-17 15:36:34.0 +0100
+++ b/TLS.pm	2016-04-08 10:34:56.0 +0200
@@ -179,7 +179,7 @@
 		croak "Invalid response for STARTTLS: $num $txt\n";
 	}
 	if(not IO::Socket::SSL::socket_to_SSL($me->{sock},
-		SSL_version	=>	"SSLv3 TLSv1")){
+		SSL_version	=>	"TLSv1")){
 			croak "Couldn't start TLS: ".IO::Socket::SSL::errstr."\n";
 	}
 	$me->hello();

Bug#784431: nsca-ng-server: fails to start with systemd because /var/run/nsca-ng is missing

[Libor Klepáč]

Hello,
can you please propagate this fix to jessie?

Thanks,

Libor

Bug#819907: gitlab: builds fails, /usr/share/gitlab/builds is not writeable

[Libor Klepáč]

Maybe, it should rather go to logs dir

Patch v2 attached, again, untested ;)

Libor


diff -ur a/debian/gitlab.links b/debian/gitlab.links
--- a/debian/gitlab.links	2016-03-13 07:21:05.0 +0100
+++ b/debian/gitlab.links	2016-04-03 20:58:06.683043165 +0200
@@ -1,6 +1,7 @@
 var/lib/gitlab/public usr/share/gitlab/public
 var/lib/gitlab/cache usr/share/gitlab/shared/cache
 var/log/gitlab usr/share/gitlab/log
+var/log/gitlab/builds usr/share/gitlab/builds
 run/gitlab usr/share/gitlab/tmp
 etc/gitlab usr/share/gitlab/config
 usr/share/javascript/jquery-history/jquery.history.min.js usr/share/gitlab/vendor/assets/javascripts/jquery.history.js
diff -ur a/debian/postinst b/debian/postinst
--- a/debian/postinst	2016-02-18 18:12:11.0 +0100
+++ b/debian/postinst	2016-04-03 21:00:37.922038434 +0200
@@ -39,13 +39,14 @@
 # Create gitlab user
 . /usr/lib/gitlab/scripts/adduser.sh
 
+gitlab_builds_log=${gitlab_log_dir}/builds
 gitlab_repo_path=${gitlab_data_dir}/repositories
 gitlab_cache_path=${gitlab_data_dir}/cache
 gitlab_uploads_path=${gitlab_data_dir}/public/uploads
 
 # Create directories and change ownership
 for i in ${gitlab_repo_path} ${gitlab_cache_path} ${gitlab_uploads_path}\
-${gitlab_pid_path} ${gitlab_log_dir} ${gitlab_shell_log}; do
+${gitlab_pid_path} ${gitlab_log_dir} ${gitlab_shell_log} ${gitlab_builds_log}; do
   mkdir -p $i
   chown -R ${gitlab_user}: $i
 done

Bug#819907: gitlab: builds fails, /usr/share/gitlab/builds is not writeable

[Libor Klepáč]

Package: gitlab
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
builds seems to fail, because it has no dir to write to

Errno::EACCES (Permission denied @ dir_s_mkdir - /usr/share/gitlab/builds):
  /usr/lib/ruby/2.3.0/fileutils.rb:253:in `mkdir'
  /usr/lib/ruby/2.3.0/fileutils.rb:253:in `fu_mkdir'
  /usr/lib/ruby/2.3.0/fileutils.rb:227:in `block (2 levels) in mkdir_p'
  /usr/lib/ruby/2.3.0/fileutils.rb:225:in `reverse_each'
  /usr/lib/ruby/2.3.0/fileutils.rb:225:in `block in mkdir_p'
  /usr/lib/ruby/2.3.0/fileutils.rb:211:in `each'
  /usr/lib/ruby/2.3.0/fileutils.rb:211:in `mkdir_p'
  /usr/share/gitlab/app/models/ci/build.rb:229:in `trace='

etc...

Here is (untested) patch to build system, to create /var/lib/gitlab/builds and 
create symlink to /usr/share/gitlab/builds

Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc7-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXAWX+AAoJEPDvjG7Cn0eOUpEQAJeqzWih80/WgbZvVkfSFG3W
+7eYJQth/M7vA3tcAGd0mr1Uh8yETILltyW3jB5BoDs0xenHI+WbiL6gfXU+U2aW
MDm9+QjPOFJrq/aq9nea5DYxcQkjdEuiyoZU8Q1EJM+iDfqGo1JUtxpXIthBIKxA
rg4aH382btXc9xlnOZPijtWi2Ba84O7Lj6gpXPg6ZntCXkLpos3KUmXMVM0wQOJB
VNgHf2Eue8Ldp2UC9xjtoHTSxHHg4j/u5ZkqPfvQhcS76dpj9Odal5fKiKMrLdtJ
uzS8mmRlNoNIu0xOMmQrTihJO15TPcLQSHdCaGQ1lavR8XGiFRUbv+mafvWfTBqZ
tVmAy3veFRp6c6CP60AroTY/qTDp6o2GCOvNkNskXGlJsu0TyNlKlb4AvT/OsnLI
5ZabfPIScSLA25RZ72VTr5896ghm0ndKd7BwQqvCYfLXj8C0Ea22pXmwKXKAHNpD
qfqVP/na81dwmCnWPO3IBjgCxUaTxIx9KA6Pjt6Z1Ga3ti4KnuYsQ/SRRa6+KEK0
O7ea/kXc2iSh1J2pjjX+12ZVuvhWDU1l3eVub53ZkznBGnRgxcfNnSTvleLd3xET
6LjbA8uj9mKLvPi7Cf0W1B9yIHr6KlEZnLsMVuVVGW8YS7x6pXI/kBCubGVIZwmy
WWXR6AWTwI1AdI1t4hrA
=qPhr
-END PGP SIGNATURE-
diff -ur a/debian/gitlab.links b/debian/gitlab.links
--- a/debian/gitlab.links	2016-03-13 07:21:05.0 +0100
+++ b/debian/gitlab.links	2016-04-03 20:46:49.909653752 +0200
@@ -1,3 +1,4 @@
+var/lib/gitlab/builds usr/share/gitlab/builds
 var/lib/gitlab/public usr/share/gitlab/public
 var/lib/gitlab/cache usr/share/gitlab/shared/cache
 var/log/gitlab usr/share/gitlab/log
diff -ur a/debian/postinst b/debian/postinst
--- a/debian/postinst	2016-02-18 18:12:11.0 +0100
+++ b/debian/postinst	2016-04-03 20:46:29.941259066 +0200
@@ -40,11 +40,12 @@
 . /usr/lib/gitlab/scripts/adduser.sh
 
 gitlab_repo_path=${gitlab_data_dir}/repositories
+gitlab_builds_path=${gitlab_data_dir}/builds
 gitlab_cache_path=${gitlab_data_dir}/cache
 gitlab_uploads_path=${gitlab_data_dir}/public/uploads
 
 # Create directories and change ownership
-for i in ${gitlab_repo_path} ${gitlab_cache_path} ${gitlab_uploads_path}\
+for i in ${gitlab_repo_path} ${gitlab_builds_path} ${gitlab_cache_path} ${gitlab_uploads_path}\
 ${gitlab_pid_path} ${gitlab_log_dir} ${gitlab_shell_log}; do
   mkdir -p $i
   chown -R ${gitlab_user}: $i

Bug#819903: gitlab: runners page not showing

[Libor Klepáč]

Package: gitlab
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
pages
/admin/runners
and
/admin/runners/$number

throws error 500
- ---
Started GET "/admin/runners" for 77.48.255.59 at 2016-04-03 00:23:37 +0200
Processing by Admin::RunnersController#index as HTML
Completed 500 Internal Server Error in 392ms (ActiveRecord: 11.5ms)
  
ActionView::Template::Error (Missing partial kaminari/_paginator with 
{:locale=>[:en], :formats=>[:html], :variants=>[], :handlers=>[:erb, :builder, 
:raw, :ruby, :coffee, :haml, :rabl]}. Searched in:
  * "/usr/share/gitlab/app/views"
  * "/usr/share/ruby-doorkeeper/app/views"
  * "/usr/share/ruby-devise/app/views"
):
64:
65: - @runners.each do |runner|
66:   = render "admin/runners/runner", runner: runner
67: = paginate @runners
  app/views/admin/runners/index.html.haml:67:in 
`_app_views_admin_runners_index_html_haml___401184490130856_81624960'
- ---

Fix is relatively simple, just add theme to paginator.
I checked upstream master and it's not there yet, probably some difference in 
debian packaging, which affects this.
I was investigating it when i was installing gitlab 8.3.0 but forget to report 
it.

Atteached patch to fix this pages

Libor


- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-rc7-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJXAVpfAAoJEPDvjG7Cn0eOVosP/1WkWKtHLbJPAD3Bi2d/t7/S
ZYNCt+P8hJwXE6L4cQn7XSyA/GqU3SG6Ah37ZAx3MHp0/1L8JHdfLVYHEiJB+mJA
MWBkjFzswke8fZ5eLkKSncjN8QiuPD7oILyBmYQBGq/UdtdG2FqEhpHuhil50aKx
rfYOkMNuJWBZwRoQT0PjGKB1n0gtf+00sIsvL7bciYpnTl2/wg6/KityaK/oMp/E
BC5cJoawDVwVLB2T1ZZcRMdqT9YIBWgssURSKyss8qea8jRbK8XCo893QHmJAAcC
FuKvChSRLBRXzN/3uqtTSliVoEsbdmrEIdcJ3n0lAz/5pprTOPRSKRpFAOakzqoQ
GD2c57KGappI2YkTZB+/NUtuPa1M+fuM35t0uDeSTYEaiO0j2NFo8bHlgMFTb2zY
AA2hhQJ9KRcX03r4obe0oX4OQRNFzDyQyy/7fA5PBPGO4sRq017xu3FLVIgvFl81
MS4zuD0QWiZ5qw3SoodSZDtIn3/CHNQ3G70qVI7lOL+7F8A6qQAnkmMQfISY8iIN
jL/dZ6lqJRI6iQ0zKZhgmmIunIOKc2MWtLiRa9/0q2p5/z06LX+FX6x2X9+u6bjc
iN05FoU40Ykh9LZjyY6mvVtgbMXDXL2/LWqNupSGVsTNNSV4WUoNwEbp/9jNzR/a
WPhvbD0jqgFDCKHslsMs
=eLvK
-END PGP SIGNATURE-
diff -ur a/app/views/admin/runners/index.html.haml b/app/views/admin/runners/index.html.haml
--- a/app/views/admin/runners/index.html.haml	2016-02-02 19:00:07.0 +0100
+++ b/app/views/admin/runners/index.html.haml	2016-04-03 19:46:41.0 +0200
@@ -64,4 +64,4 @@
 
 - @runners.each do |runner|
   = render "admin/runners/runner", runner: runner
-= paginate @runners
+= paginate @runners, theme: "gitlab"
diff -ur a/app/views/admin/runners/show.html.haml b/app/views/admin/runners/show.html.haml
--- a/app/views/admin/runners/show.html.haml	2016-02-02 19:00:07.0 +0100
+++ b/app/views/admin/runners/show.html.haml	2016-04-03 19:47:59.0 +0200
@@ -85,7 +85,7 @@
   = form_for [:admin, project.namespace.becomes(Namespace), project, project.runner_projects.new] do |f|
 = f.hidden_field :runner_id, value: @runner.id
 = f.submit 'Enable', class: 'btn btn-xs'
-= paginate @projects
+= paginate @projects, theme: "gitlab"
 
   .col-md-6
 %h4 Recent builds served by this runner

Bug#815465: gitlab wiki content doesn't show up

[Libor Klepáč]

Package: gitlab
Followup-For: Bug #815465

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
can you please try this little patch?
I use it on gitlab 8.3.0 packages from Praveen.


Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW1+gjAAoJEPDvjG7Cn0eO2FAP+QFh6+BgS6T1B8H5A/b+rkh5
lssTMC9yAOXuANucPzyKq2kv/PrmLJj9FeuRo3e1CmeWSl+ymBEz7/F0vRZIr5e8
tlXxdHjRHECc2Yix8D0ldOf4/hCiCVZXhM1vr+jJk5NY1rWwntL9Mir7PmIw9sgC
6+/yVYQoHo7YtuTIMKnzx7UyBQhuPXV7d/YBqR8Z9OAunEcHE8M+lZfDfhHQI/f6
NqDoF00BCYE5rUU84g4zP63+gObFlPlBz/MTWbF3v/3cWVqSVn9vNhQLKnUGc/g+
AQIAk2s5r7RIi9fsERB2I/PT4nfauMqYdWYDxYrnUQjHHMaBlvX+Ir9zrHQ1SG6h
QXwwScyH4wq37y+ehqhi3u4P0jb3MpDfNsQj4JxeFi1XiBF+dhpbQmJ2VEizSpzc
FZHsp/YMBqSVwrfCE2oqXC6c/ENUb13Cz8rzmz+G1BE2HjMzMNHmFShfYKmdlCyC
XlM6f+k908VNKKvdTPkYkB72TO/zc0SgFp9ODdK6/31ERKiKVPhbDt9mkUbsI6Xk
uR0At9LjSWUZV6bCk4z5LJQq4kwNqPkO0K2WLI0Pdsy8qRe9jm/YuwzAXO+PR7YL
8NVTzBQChufe5sRVBggEtEbbQhsMtFNDqxCgz43Rhqsldsi6NkOzXVbC/mTyDOkV
0JMQYM/Z3hWamvZ3FXCS
=fEO2
-END PGP SIGNATURE-
diff -ur a/app/models/wiki_page.rb b/app/models/wiki_page.rb
--- a/app/models/wiki_page.rb	2016-01-23 17:45:00.0 +0100
+++ b/app/models/wiki_page.rb	2016-03-03 08:26:25.256512379 +0100
@@ -62,7 +62,7 @@
   # The raw content of this page.
   def content
 @attributes[:content] ||= if @page
-@page.raw_data
+@page.text_data
   end
   end
 

Bug#809812: ruby-gollum-rugged-adapter: Set committer to the same actor as author.

[Libor Klepáč]

Package: ruby-gollum-rugged-adapter
Version: 0.4.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
can you please apply this patch to source
https://github.com/jhominal/rugged_adapter/commit/10b6da7d175b78a89436400ffd3526e3a4a0e382

it fixes creating new wiki page in gitlab

With regards,
Libor


- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWik0SAAoJEPDvjG7Cn0eO67MQAJHbagl14ei+dx6rd2V6DTkx
5jRyyjhiw2JNK9wLcEMc0v2da+D5n3hf/YF8eri14G7s2D2Y6P0UefqilAkncnCP
0ysylUce/xrGH3WDp+TkVc+azqQTjBa+YVHAGCNwMUnEklgvqTsZr27FG740+qAa
Iy8C/pVgK08wvaH7HXYB0H+Hq8am6adY44abidVyx3ajPKXoqEpJniiMwW3/I40V
QodoWnpmkLmnBMyHhDaNDFnqtVzj13nQpoZg5ufyx3nETQFrYnddrclCGU9Zs0rn
NXpOwMZ7+snFr0wFtIsVgEgUvQdG7ZzPRxVHXW8c5mh+FgfUJ61bTWdOOpzoenjL
wlJ602l2VWEZ8bNpwBVqIo4UD7rHDymFzSd9EU15UG3wR3G0FtJVz+xWiecGl1HB
cC/VCUYeAoY6e035BNXOIgkI7sId+yG7fwQZXTaAlU2BWCRE3f0W1SS3idnQAnp4
8taECc8/bp4SzYuCSzsDzZHEtZlb70Cn6y2JYbAuIcjcSUhOW0bNcDDe3dXjMg2w
wXAnw6pvmjNuWcy0XWYIYE5F/ucodgHdkFhjhPfSQSP+OiGw1HZfPBipHV4w03Xj
ZaxC0ydqRzvhHhLBFr0FhUuotaSq+SYL2LDnG42PpHbzkatiLErgtWqxiJaiOotX
o/Z//6VMXZf1F5ROVGGh
=D+q8
-END PGP SIGNATURE-

Bug#809559: ruby-activerecord-session-store: Missing epoch in dependency on ruby-actionpack

[Libor Klepáč]

Hello,
I have been testing it on my computer, which has only unstable and 
experimental, it doesn't 
have yours repo.

You can check this version dependency also here:
https://packages.debian.org/sid/ruby-activerecord-session-store

With regards,
Libor


On Fri, 01 Jan 2016 13:54:43 +0100 =?utf-8?b?TGlib3IgS2xlcMOhxI0=?= 
 wrote:
> Package: ruby-activerecord-session-store
> Version: 0.1.1-1
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Hello,
> it seems to me, that dependency on
> ruby-actionpack (<< 5)
> is missing epoch 2
> 
> With regards,
> Libor
> 
> - -- System Information:
> Debian Release: stretch/sid
>   APT prefers experimental
>   APT policy: (700, 'experimental'), (700, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.3.0-trunk-amd64 (SMP w/4 CPU cores)
> Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages ruby-activerecord-session-store depends on:
> ii  ruby1:2.2.4
> pn  ruby-actionpack 
> pn  ruby-activerecord   
> pn  ruby-railties   
> ii  ruby2.2 [ruby-interpreter]  2.2.3-2
> 
> ruby-activerecord-session-store recommends no packages.
> 
> ruby-activerecord-session-store suggests no packages.
> 
> - -- no debconf information
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iQIcBAEBCAAGBQJWhncIAAoJEPDvjG7Cn0eOTo8P/3B2HLaWJbtv3sbAl94TaP8M
> noQUX08KsxnsXqSt4hXrdPqt4C3Vn14j7vFMa8m2WI77C0z40sD2qMZ8X6sclcyW
> pssvEgLLaHeotjl/EgnW7DOTQeXIUGwNg6AakZdqO8fQo/GlIMZIMcGWDy4RVlFf
> Q4hqg4DkGUCnwlnRAxXUpdCK5gs7LEgdzNBVrvgKMCv8Z99iKZdN2wmwWKgG/Bgu
> IzhlSmgaY6EDRW0JpNWqWCY856qurNqpU0F168JZh6ZAuuKVRaOpCVxQ8aub06FP
> LFGXf0HqU2ZAXcprShb8vcxtSSLr0cbosPE7fw4FA1rE4v5IrbEP87LA9Pp8Sy/Y
> 11fWSvObtvTBfhBEO/5yzjlb49VpdOy6sdJgjbCDd/P43t0WD4NieJf2ZSAE1Nga
> Ymd1wFI7hylGEnlAChBdbCh7MdcgmrhYhkEkOhsOD7SVS8pNZMzhMlQZs4MpcfjP
> pjTMrPTIMFWG/y+9TCiKZn6GWlJ6adi9B6lwc2U/4ao6qFGg7DSYOJ8Gj8+x+aBl
> E6EkYHZGMiai0AXbvVRKxeP+VURwjacOGIRr3CNP6myb1WTbPUkY0ZijmyKZf8Xt
> Ow3RFm9+SBqRUshABfNZQyFbGbU3+tP7VJouliPJna3JQ5k5/5ZybLAPjvKqxhPt
> 4xajJAvyvvB4K4K9uJcQ
> =bcf5
> -END PGP SIGNATURE-
> 
> 

Bug#809560: ruby-activerecord-session-store: File conflict with ruby-devise

[Libor Klepáč]

Package: ruby-activerecord-session-store
Version: 0.1.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
when installing gitlab I also hit this problem

LANG=C dpkg -i ruby-activerecord-session-store_0.1.1-1_all.deb 
(Reading database ... 195261 files and directories currently installed.)
Preparing to unpack ruby-activerecord-session-store_0.1.1-1_all.deb ...
Unpacking ruby-activerecord-session-store (0.1.1-1) over (0.1.1-1) ...
dpkg: error processing archive ruby-activerecord-session-store_0.1.1-1_all.deb 
(--install):
 trying to overwrite 
'/usr/lib/ruby/vendor_ruby/generators/active_record/templates/migration.rb', 
which is also in package ruby-devise 3.5.2-2
Errors were encountered while processing:
 ruby-activerecord-session-store_0.1.1-1_all.deb

I don't know, which one should be there

With regards,
Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ruby-activerecord-session-store depends on:
ii  ruby1:2.2.4
ii  ruby-actionpack 2:4.2.5-1
ii  ruby-activerecord   2:4.2.5-1
ii  ruby-railties   2:4.2.5-1
ii  ruby2.2 [ruby-interpreter]  2.2.3-2

ruby-activerecord-session-store recommends no packages.

ruby-activerecord-session-store suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWhnoOAAoJEPDvjG7Cn0eOzdQP/27mSxBtL/dy3JbC601PbNYo
XTdQHuEZi61vikUoLZi1Sp9k/FBvr32298JXWyBDp0b6eecoEgIDwampNlRAsnED
xsNzGDBFSxh5hWiEujz4UidCviBFWjGm3Whh6G5wVDTdB38bvaRqcv9UJVclVkUE
jp7tb327PD443AbQtv0fg6fcY4WnSn4xnXh82vZ4l/hGx42uE/RFPpdVtKisvuGw
RddslKIjg5PphjnokDQIQmRtUi49Qv96NKP3jitctxZtXdSf8cIhs/9Qt7Qi72WQ
s4FhYKU/12aHo3unEcv8nTl/LNT8bh4x+Rfx5z1DH+RdlkCCsCk4m1Goz4UH7zbL
c0kJSvZ3PCGJfwU+bLuQ6gA1XQkVFgl6w2YDPo1AT7lrG1pcW0vHwlmI8L9KlBs1
4WdZUVmSkQh4tkZ6f+92yUIUgMC994VZFkSH934ssHQUe7tZDk2+FXt2nCtXOJ6g
H/1uaxS+g2QdNQh26jsKNOJkyX7RJ6a6lpkq3c9szjvnpg9/tPdimffrCwHyc/cm
9YQZqP4iBr15hMd7iUXs6e4+c0q4XAD0riqh5CF9rZAWHwCDDiggjVx24AO0VWwE
JgrMtfDtD/5QItrPSRTcZDDtqj39B8x8IKnLWhE+nDGZ8ejK51sUdYbmlaBpkp7x
g2oQ4lo1veQsIb+Za+Rb
=+bl4
-END PGP SIGNATURE-

Bug#809559: ruby-activerecord-session-store: Missing epoch in dependency on ruby-actionpack

[Libor Klepáč]

Package: ruby-activerecord-session-store
Version: 0.1.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
it seems to me, that dependency on
ruby-actionpack (<< 5)
is missing epoch 2

With regards,
Libor

- -- System Information:
Debian Release: stretch/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages ruby-activerecord-session-store depends on:
ii  ruby1:2.2.4
pn  ruby-actionpack 
pn  ruby-activerecord   
pn  ruby-railties   
ii  ruby2.2 [ruby-interpreter]  2.2.3-2

ruby-activerecord-session-store recommends no packages.

ruby-activerecord-session-store suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWhncIAAoJEPDvjG7Cn0eOTo8P/3B2HLaWJbtv3sbAl94TaP8M
noQUX08KsxnsXqSt4hXrdPqt4C3Vn14j7vFMa8m2WI77C0z40sD2qMZ8X6sclcyW
pssvEgLLaHeotjl/EgnW7DOTQeXIUGwNg6AakZdqO8fQo/GlIMZIMcGWDy4RVlFf
Q4hqg4DkGUCnwlnRAxXUpdCK5gs7LEgdzNBVrvgKMCv8Z99iKZdN2wmwWKgG/Bgu
IzhlSmgaY6EDRW0JpNWqWCY856qurNqpU0F168JZh6ZAuuKVRaOpCVxQ8aub06FP
LFGXf0HqU2ZAXcprShb8vcxtSSLr0cbosPE7fw4FA1rE4v5IrbEP87LA9Pp8Sy/Y
11fWSvObtvTBfhBEO/5yzjlb49VpdOy6sdJgjbCDd/P43t0WD4NieJf2ZSAE1Nga
Ymd1wFI7hylGEnlAChBdbCh7MdcgmrhYhkEkOhsOD7SVS8pNZMzhMlQZs4MpcfjP
pjTMrPTIMFWG/y+9TCiKZn6GWlJ6adi9B6lwc2U/4ao6qFGg7DSYOJ8Gj8+x+aBl
E6EkYHZGMiai0AXbvVRKxeP+VURwjacOGIRr3CNP6myb1WTbPUkY0ZijmyKZf8Xt
Ow3RFm9+SBqRUshABfNZQyFbGbU3+tP7VJouliPJna3JQ5k5/5ZybLAPjvKqxhPt
4xajJAvyvvB4K4K9uJcQ
=bcf5
-END PGP SIGNATURE-

Bug#789319: audit: sometimes doesn't report correct filename

[Libor Klepáč]

Package: src:linux
Version: 3.16.7-ckt11-1
Severity: normal

Dear Maintainer,
can you please consider patching kernel to report correct filenames in audit?

It was already patched in Ubuntu, i think
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439441

Patch is here
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4a92843601ad0f5067f441d2f0dca55bbe18c076

Thank you very much,

Libor


-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vgEOSVPS1Disk1-lvSystem ro 
quiet

** Not tainted

** Kernel log:
[1.372300] sd 0:0:2:0: Attached scsi generic sg2 type 0
[1.372365] sr 2:0:0:0: Attached scsi generic sg3 type 5
[1.373216]  sdc: unknown partition table
[1.373337] sd 0:0:2:0: [sdc] Attached SCSI disk
[1.568645] e1000 :02:01.0 eth1: (PCI:66MHz:32-bit) 00:50:56:93:77:84
[1.568649] e1000 :02:01.0 eth1: Intel(R) PRO/1000 Network Connection
[1.576182] device-mapper: uevent: version 1.0.3
[1.576239] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: 
dm-de...@redhat.com
[1.701961] PM: Starting manual resume from disk
[1.701966] PM: Hibernation image partition 254:1 present
[1.701967] PM: Looking for hibernation image.
[1.702165] PM: Image not found (code -22)
[1.702167] PM: Hibernation image not present or could not be loaded.
[1.743857] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: 
(null)
[2.276778] systemd[1]: Cannot add dependency job for unit dbus.socket, 
ignoring: Unit dbus.socket failed to load: No such file or directory.
[2.276801] systemd[1]: Cannot add dependency job for unit 
display-manager.service, ignoring: Unit display-manager.service failed to load: 
No such file or directory.
[2.467839] systemd-udevd[173]: starting version 215
[2.673589] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[2.673594] ACPI: Power Button [PWRF]
[2.692285] random: nonblocking pool is initialized
[2.696069] ACPI: AC Adapter [ACAD] (on-line)
[2.745695] vmw_vmci :00:07.7: Found VMCI PCI device at 0x11080, irq 16
[2.745798] vmw_vmci :00:07.7: Using capabilities 0xc
[2.746041] vmw_vmci :00:07.7: irq 72 for MSI/MSI-X
[2.746110] vmw_vmci :00:07.7: irq 73 for MSI/MSI-X
[2.746570] Guest personality initialized and is active
[2.746642] VMCI host device registered (name=vmci, major=10, minor=59)
[2.746643] Initialized host personality
[2.768182] [drm] Initialized drm 1.1.0 20060810
[2.787716] piix4_smbus :00:07.3: SMBus Host Controller not enabled!
[2.788428] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[2.815015] parport_pc 00:05: reported by Plug and Play ACPI
[2.815265] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
[2.851561] [drm] DMA map mode: Using physical TTM page addresses.
[2.851655] [drm] Capabilities:
[2.851657] [drm]   Rect copy.
[2.851658] [drm]   Cursor.
[2.851659] [drm]   Cursor bypass.
[2.851660] [drm]   Cursor bypass 2.
[2.851660] [drm]   8bit emulation.
[2.851661] [drm]   Alpha cursor.
[2.851662] [drm]   Extended Fifo.
[2.851663] [drm]   Multimon.
[2.851664] [drm]   Pitchlock.
[2.851665] [drm]   Irq mask.
[2.851666] [drm]   Display Topology.
[2.851666] [drm]   GMR.
[2.851667] [drm]   Traces.
[2.851668] [drm]   GMR2.
[2.851669] [drm]   Screen Object 2.
[2.851670] [drm] Max GMR ids is 64
[2.851672] [drm] Max number of GMR pages is 65536
[2.851673] [drm] Max dedicated hypervisor surface memory is 163840 kiB
[2.851674] [drm] Maximum display memory size is 4096 kiB
[2.851675] [drm] VRAM at 0xec00 size is 4096 kiB
[2.851676] [drm] MMIO at 0xfe00 size is 256 kiB
[2.851678] [drm] global init.
[2.851726] [TTM] Zone  kernel: Available graphics memory: 2030496 kiB
[2.851728] [TTM] Initializing pool allocator
[2.851733] [TTM] Initializing DMA pool allocator
[2.852076] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[2.852079] [drm] No driver support for vblank timestamp query.
[2.852416] [drm] Screen objects system initialized
[2.852421] [drm] Initialized vmwgfx 2.6.0 20140325 for :00:0f.0 on 
minor 0
[2.960345] EXT4-fs (dm-0): re-mounted. Opts: 
discard,user_xattr,errors=remount-ro
[3.004365] ppdev: user-space parallel port driver
[3.061823] input: PC Speaker as /devices/platform/pcspkr/input/input3
[3.104204] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: 
(null)
[3.163351] SSE version of gcm_enc/dec engaged.
[3.165743] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni)
[3.172401] alg: No test for crc32 (crc32-pclmul)
[3.203331] Adding 1949692k swap on 

Bug#470417: some people fixed it already

[Libor Klepáč]

Hello,
any official progress on support of ipv6, please?

I have recently upgraded one of servers from Squeeze to Jessie (with Wheezy 
inter-step for few minutes ;) to find out, that we used ipv6 patched fail2ban 
on  
Squeeze. 

I tried to clone
https://github.com/yarikoptic/fail2ban.git
there are some ipv6 branches, but ?none? is for fail2ban version in Jessie.

Can you please recommend one of those branches, I'm ready to run some 
version lower than version in Jessie, because ipv6 support is important for us 
on 
this host.

Thanks for suggestion,
Libor




 On Thu, 05 Jul 2012, klemens z wrote:
  Hi bug,
 
 hello H20+additives ;-)
 
  just want to mention this:
 
  http://www.isalo.org/wiki.debian-fr/index.php?title=Fail2ban
 
  Looks like they have solved the ipv6  fail2ban issues.
 
  Not sure if this is the author, or just somebody's hack - at least
  sounds promising.
 yes
 
 see
 https://github.com/fail2ban/fail2ban/issues/39
 and work of
 https://github.com/Th4nat0s/fail2ban
 
 so it is somewhat on the way
 
  open-source rocks!
 
 indeed
 
 -- 
 Yaroslav O. Halchenko
 Postdoctoral Fellow,   Department of Psychological and Brain Sciences
 Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
 Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
 WWW:   http://www.linkedin.com/in/yarik
 
 
 

Bug#747413: lsb-release: lsb_release takes correctly parses /etc/debian_version, forgets about it, then calling apt-cache policy making python startup unbearably slow

[Libor Klepáč]

Package: lsb-release
Version: 4.1+Debian13
Followup-For: Bug #747413

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello,
i still have problem with this, it slows vmware player.
After applying patch from original bug report, problem seems to go away. 

Strace of lsb_release -r before is 56MB in size and it takes almost minute to 
finish
, after it finishes instantly with  113kB strace.

Libor

- -- Package-specific info:
lsb_release output
- -*- -*- -*- -*- -*-
Distributor ID: Debian
Description:Debian GNU/Linux testing/unstable (jessie)
Release:testing/unstable
Codename:   jessie
- -*- -*- -*- -*- -*-
Apt policy
- -*- -*- -*- -*- -*-
Package files:
 100 /var/lib/dpkg/status
 release a=now
 500 http://repos-source.zend.com/zend-server/6.0/deb_ssl1.0/ server/non-free 
i386 Packages
 release o=Zend,a=5.6.0,n=server,l=Zend Server,c=non-free
 origin repos-source.zend.com
 500 http://repos-source.zend.com/zend-server/6.0/deb_ssl1.0/ server/non-free 
amd64 Packages
 release o=Zend,a=5.6.0,n=server,l=Zend Server,c=non-free
 origin repos-source.zend.com
 500 http://packages.pulse-eight.net/ubuntu/ quantal/stable amd64 Packages
 release o=packages.pulse-eight.net,a=quantal,n=quantal,l=Pulse-Eight 
Ubuntu Repository,c=stable
 origin packages.pulse-eight.net
 500 http://mozilla.debian.net/ experimental/iceweasel-aurora amd64 Packages
 release o=Debian Mozilla Team,a=experimental,n=experimental,l=Debian 
Mozilla Team,c=iceweasel-aurora
 origin mozilla.debian.net
 500 http://mozilla.debian.net/ experimental/iceweasel-beta amd64 Packages
 release o=Debian Mozilla Team,a=experimental,n=experimental,l=Debian 
Mozilla Team,c=iceweasel-beta
 origin mozilla.debian.net
 500 http://ppa.launchpad.net/mikevaughn/omnilinux/ubuntu/ saucy/main amd64 
Packages
 release 
v=13.10,o=LP-PPA-mikevaughn-omnilinux,a=saucy,n=saucy,l=omniLinux,c=main
 origin ppa.launchpad.net
 500 http://ppa.launchpad.net/mikevaughn/omnilinux/ubuntu/ quantal/main amd64 
Packages
 release 
v=12.10,o=LP-PPA-mikevaughn-omnilinux,a=quantal,n=quantal,l=omniLinux,c=main
 origin ppa.launchpad.net
 500 http://ppa.launchpad.net/blueleaflinux/ppa/ubuntu/ quantal/main amd64 
Packages
 release v=12.10,o=LP-PPA-blueleaflinux,a=quantal,n=quantal,l=Blue Leaf 
Linux ppa,c=main
 origin ppa.launchpad.net
 500 http://linux.dell.com/repo/community/ubuntu/ wheezy/openmanage amd64 
Packages
 release o=Dell Inc,a=wheezy,n=wheezy,l=Dell OMSA Archive,c=openmanage
 origin linux.dell.com
 703 file:/root/debs/ ./ Packages
 release o=rebuild kde,a=unstable,c=
 500 http://deb.opera.com/opera-beta/ sid/non-free amd64 Packages
 release o=Opera Software ASA,a=stable,n=stable,l=The Opera web 
browser,c=non-free
 origin deb.opera.com
 500 http://ppa.launchpad.net/freenx-team/ppa/ubuntu/ lucid/main amd64 Packages
 release v=10.04,o=LP-PPA-freenx-team,a=lucid,n=lucid,l=FreeNX Stable 
PPA,c=main
 origin ppa.launchpad.net
 600 http://ftp.uni-kl.de/debian-multimedia/ sid/main i386 Packages
 release v=7.0,o=Unofficial Multimedia 
Packages,a=unstable,n=sid,l=Unofficial Multimedia Packages,c=main
 origin ftp.uni-kl.de
 600 http://ftp.uni-kl.de/debian-multimedia/ sid/main amd64 Packages
 release v=7.0,o=Unofficial Multimedia 
Packages,a=unstable,n=sid,l=Unofficial Multimedia Packages,c=main
 origin ftp.uni-kl.de
 601 http://ftp.uni-kl.de/debian-multimedia/ experimental/main i386 Packages
 release v=None,o=Unofficial Multimedia 
Packages,a=experimental,n=experimental,l=Unofficial Multimedia Packages,c=main
 origin ftp.uni-kl.de
 601 http://ftp.uni-kl.de/debian-multimedia/ experimental/main amd64 Packages
 release v=None,o=Unofficial Multimedia 
Packages,a=experimental,n=experimental,l=Unofficial Multimedia Packages,c=main
 origin ftp.uni-kl.de
 701 http://debian-bcom.bcom.dmz/ wheezy/orig i386 Packages
 release o=Business Communication,a=wheezy,n=wheezy,l=Bcom packages,c=orig
 origin debian-bcom.bcom.dmz
 701 http://debian-bcom.bcom.dmz/ wheezy/desktop-rebuild amd64 Packages
 release o=Business Communication,a=wheezy,n=wheezy,l=Bcom 
packages,c=desktop-rebuild
 origin debian-bcom.bcom.dmz
 701 http://debian-bcom.bcom.dmz/ wheezy/rebuild amd64 Packages
 release o=Business Communication,a=wheezy,n=wheezy,l=Bcom 
packages,c=rebuild
 origin debian-bcom.bcom.dmz
 701 http://debian-bcom.bcom.dmz/ wheezy/orig amd64 Packages
 release o=Business Communication,a=wheezy,n=wheezy,l=Bcom packages,c=orig
 origin debian-bcom.bcom.dmz
 701 http://debian-bcom.bcom.dmz/ wheezy/bcom amd64 Packages
 release o=Business Communication,a=wheezy,n=wheezy,l=Bcom packages,c=bcom
 origin debian-bcom.bcom.dmz
 701 http://debian-bcom.bcom.dmz/ wheezy/kernel amd64 Packages
 release o=Business Communication,a=wheezy,n=wheezy,l=Bcom packages,c=kernel
 origin debian-bcom.bcom.dmz
 500 http://ftp.cz.debian.org/debian/ unstable/non-free 

Bug#728435: lxc-stuff breaks bash completion

[Libor Klepáč]

Package: lxc-stuff
Version: 1.0.0~alpha2-3
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,
instalation of lxc-stuff 1.0.0~alpha2-3 breaks bash, because it installs lxc 
init file into /etc/bash_completion.d

With regards
Libor Klepac


- -- System Information:
Debian Release: jessie/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lxc-stuff depends on:
ii  debconf [debconf-2.0]  1.5.51
ii  lxc1.0.0~alpha2-3

Versions of packages lxc-stuff recommends:
ii  debootstrap  1.0.55

Versions of packages lxc-stuff suggests:
ii  debian-keyring  2013.07.31
ii  gpgv1.4.15-1.1
pn  live-debconfig-doc  none
ii  rsync   3.1.0-2

- -- debconf information:
  lxc/directory: /var/lib/lxc
  lxc/auto: true
  lxc/title:

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCAAGBQJSc4QdAAoJEPDvjG7Cn0eOk/8P/3t+diI0y59y5sUSEe4f92kY
qkLm50qEpBmuMojncNjIIynkVkzxbub21BfMFkrIdtO43FVBLysW660eyw594UWW
nLQYwQXGTbJ0xKR57srPsvFgoRWPlt2FzUwAUYw2PRtVH9IiG1Qf3P4XExfttR7V
TPYN6hG89wihH38snwV5yeEhvWexC0PV/rMNlMcC/j8Mu8eZjoLaAsSeOkg8sABW
4N6pjZaprsCL8VshOaEICo3JDGbA1sKGF26+Tv6CkJaT9vACP1fIUi1SpRZindTk
0/kKMqkErDqCKvHcKYK9zDXDphvfih1vF4H7OBEUQwYtyoUCUZU6wF1wvStxBDYp
sppwu1gfsHSZPNP/l0ZVIDVF1sk62vndj12+gq++VVbg7jPj4PlIlLXBWViisRg6
iv03ZjocZxor+SchT/vDmHhFOHJHNuczPLqh0liHNWfomzH9l7K4oTLKMNxe44Rw
EIMT8EGvPDQ0eBM7xxe7Bs6IJmn1dzWNIrXU3cnflgWcZjLmGv0mW0b1q6H/LJ2G
listZA07dpNj5Va0UXpRT8m0n7/V/RrixWQDyvXkO8ni4kvj3g1fFYOTdhkHBpcF
2Kfy+DFMGFrcny9w8pZmQVI/q0lysTiZD+EwPaI7VNBX00ZwtMcHvO2Auk1pNIc9
YXd0iW1aVNGWMrk+DqPv
=JXOO
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#684364: target: reports vfs_writev() returned -28 on iscsi activity

[Libor Klepáč]

Hello,
problem hit again
kernel is 
ii  linux-image-3.2.0-3-amd643.2.23-1amd64  
  Linux 3.2 for 64-bit PCs

During backup to iscsi file located on btrfs, btrfs runs out of space 
vfs_writev() returned -28

# btrfs filesystem show --all-devices /dev/sdb
failed to read /dev/sr0: No medium found
failed to read /dev/fd0: No such device or address
Label: none  uuid: b99c5f6a-dce2-4ba5-9fc1-4394847f45be
Total devices 1 FS bytes used 620.12GB
devid1 size 635.00GB used 635.00GB path /dev/sdb

Btrfs Btrfs v0.19

#btrfs filesystem df /mnt/tmp
Data: total=626.77GB, used=617.32GB
System, DUP: total=8.00MB, used=84.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=4.11GB, used=2.80GB

#df
/dev/sdb   665845760 653174560   9905632  99% /mnt/tmp

#du -cms /mnt/tmp/iscsi/*
51201   /mnt/tmp/iscsi/iscsiCallCentrum
562575  /mnt/tmp/iscsi/iscsiSBS

#mount
/dev/sdb on /mnt/tmp type btrfs (rw,noatime,compress=lzo,nospace_cache)

With regards
Libor

signature.asc
Description: This is a digitally signed message part.

Bug#686737: alsa-source: Please package upstream version 1.0.25 for jack sensing feature

[Libor Klepáč]

Package: alsa-source
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,
can you please package upstream version 1.0.25 for wheezy release?
It supports jack sensing feature, so output in pulseaudio switches automaticaly 
from speakers to headphones after pluging it in.
Kernel 3.2.x in wheezy has alsa version 1.0.24, which doesn't support it.

With regards,
Libor

- -- System Information:
Debian Release: wheezy/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.5-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages alsa-source depends on:
ii  bzip2  1.0.6-4
ii  debconf [debconf-2.0]  1.5.46
ii  debconf-utils  1.5.46
ii  debhelper  9.20120830
ii  dpkg-dev   1.16.8
ii  gcc [c-compiler]   4:4.7.1-1
ii  gcc-4.6 [c-compiler]   4.6.3-9
ii  gcc-4.7 [c-compiler]   4.7.1-7
ii  make   3.81-8.2

Versions of packages alsa-source recommends:
ii  fakeroot   1.18.4-2
ii  kernel-package 12.036+nmu3
ii  linux-headers-3.5-trunk-amd64 [linux-headers]  3.5.2-1~experimental.1
ii  module-assistant   0.11.4

alsa-source suggests no packages.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQRv0/AAoJEPDvjG7Cn0eOi4gP/iBDEaS7M9fb3OMR9WrfVX87
MdZM7aifEvqe5kDbGHSG280haio4DhQhNk6mCYWXJ88v8sTB0U+49vFyg/SSW9RM
ln2qKNUCjrM9xKslmHG6bRza8IGAUdWDB6/lhHnWM1MiWdNs6yEo/Gr45ekKuZop
tv6DOle89oRL6f18akjqyTB4zVt5idd1ik5+33gNde/gpjVyQ9WJF4qG4qEHMUK/
XTSEPyRrv0JVQ7r8hWDG5qofbauTTlPwgHq9dVEw+WfgqvNyU+YMldk7EScU8D0N
Ixiofq5vzAYrFkbhCmfBw1fudHn5qJvQNaWRnODvbs4cc+zicKd33uAFw3SjjmzK
82CGXXw7yJGUv5ufptKsw/U+5Q3aFWdz+EsK0u9JL4hV+UA/P743rPJQCWh3nS8w
HAQEkQ+jtAKB6nBuoRwN9lqKjGyALbUfuCU9Y1tyuoKN3jCt2IbKwtPM7MnweCo7
hrUCTXYRgFb7nGecJABA65KKwKTOi1rrk3aSc+0PuOJTFlRRJjWbEWWLI/UnTw5m
5+Euz8UjFQDM2IikGPIHN2DBam+G6oFfxun7I9kuyoAktdUcDfgoG8QQpn99zWrp
xKAGt4YSdNbuZ6q4i2BE+Ek+QlGWsxRhC0azZ3bkws2leKfvpBnqtt7CX5rWbkPh
07ZEJ00yMn260kT+5RP3
=KqtJ
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#684864: debian-installer: partman: please add acl option to mount options

[Libor Klepáč]

Package: debian-installer
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hello installer maintainers,
would it be possible to add acl option to mount options during installation?
It should trigger installation of acl package, if present.

With regards,
Libor

- -- System Information:
Debian Release: wheezy/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJQKg3kAAoJEPDvjG7Cn0eOfn8P+gMfD2xv97dnDFzIWeI6ABgx
7+UNwZ4KCy6vu9ikBL4PcGj0FCSLIMkykF18DaoiolAuizOPfxHPXM/FndrmZhoq
Ghq3JJW7u1AeeIJH7M3TtyPT5iWaKzAjDuQsIMCjK+SzW0rUl/oNeAMzdHy8dWeJ
IIicJSveIlbnXSu5OMvp6WCnye+SIr5APeEnfDxNy0P04pH8yHQ67fIDa09YhXo1
NOP4xGDTFITE8UzHY1Whk05CilS6wAHlpc4F+w7UcEpp1E58XtA+ZQnvuhrUQ1s/
LdeIZ1HasCTzfZ6YfW+opvJIxrR6rQtGfX5EWIh+VYmz6IyTnWZVlPQTstI/kRm+
abgeMIA+27vKe67CpaOl4HZ0+8teSSzCVkwZvdfrFdK4XCcR+QxFsjP1251HW4yD
1rqppuwEZ5Tt+aHAA4v4YIzCjUwO+AQRwgZM97TEpcFRciptHHyCZnaMs3vv4mDb
cShMXkXCIgyXwPfx8odRCbeQYP1300lC8dU7LvCz0LXcRJhZsi9YRgtdwsX5VexQ
/0+0qzVvdvjGOAY/CdIu8DjWc+RdPHFKJpzkJlo2DMvt6Y98RvpSW/EX8f+rnFQE
e06Yno9qBdmbZ/YlsIPrMMOJQ2mNYi9u9ijSC1EE3EfxTvs56MSvNKkGZ5bzTwrZ
RoDPxFZV9e/qaJ8QtZ9/
=UJAV
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#684364: target: reports vfs_writev() returned -28 on iscsi activity

[Libor Klepáč]

Hello,

Dne Sunday 12 August 2012 23:09:35, Ben Hutchings napsal(a):
 On Thu, 2012-08-09 at 09:40 +0200, root wrote:
  Package: linux-image-3.2.0-3-amd64
  Version: 3.2.21-3
  Severity: normal
  
  Hello,
  i'm using this virtual machine to export iscsi targets for windows
  machines to backup. It has 620GB btrfs partition with 550GB iscsi file_io
  LUN exported. I'm using btrfs snapshots to transport (consistent copy of)
  this big file to secondary backup storage (qnap and usb disk) - it takes
  around 12 hours to transport - thats reason to use snapshots. Everything
  was working fine, until i run out of space on btrfs (because of snapshot
  and fullbackup from windows combination). 
   Since than, i have created fresh filesystem and create empty new file to
   export over iscsi. 
  Now, around 250GB of writen data do iscsi file, kern.log starts to fill
  with these messages vfs_writev() returned -28
  
  It keeps to show on every access to iscsi (even rescan disk operation in
  windows triggers it)
 Any read access may change the image file's access time (atime) if you
 don't use the 'noatime' mount option.  On btrfs, metadata changes may
 allocate more disk space.
 
You are right, i forgot noatime option on mount

  I was suspecting btrfs, but there is no oops in kern.log.
  
  I tried to google this error and found nothing relevant.
 
 Error 28 is ENOSPC: No space left on device.
 
  I tried to reset everything (new filesystem, empty file, remove/add target
  from windows) and this errors comes back after writing approx. 250GB of
  data. (Before problem, file was filled to around 540GB).
  
  Size now:
  # du -cms iscsiSBS
  244561  iscsiSBS
 
 [...]
 
 What does 'btrfs filesystem df /btrfs' say (substitute the actual
 mountpoint for the btrfs volume)?
It said (i saved this before running balance)
Data: total=578.01GB, used=263.03GB
System, DUP: total=8.00MB, used=72.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=1.73GB, used=1.03GB
Metadata: total=8.00MB, used=0.00


I tried this - is it ok, it doesn't free used after rm?

# dd if=/dev/zero of=/mnt/tmp/1 bs=100M count=10
# rm /mnt/tmp/1
# btrfs filesystem df /mnt/tmp/
Data: total=1.01GB, used=0.00
System, DUP: total=8.00MB, used=4.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=1.00GB, used=1.27MB
Metadata: total=8.00MB, used=0.00

# dd if=/mnt/backupWin/iscsi/iscsiSBS of=/mnt/tmp/1 bs=100M count=10
10+0 records in
10+0 records out
1048576000 bytes (1.0 GB) copied, 22.0851 s, 47.5 MB/s

# btrfs filesystem df /mnt/tmp/
Data: total=1.01GB, used=1000.00MB
System, DUP: total=8.00MB, used=4.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=1.00GB, used=1.41MB
Metadata: total=8.00MB, used=0.00

# rm /mnt/tmp/1 
# btrfs filesystem df /mnt/tmp/
Data: total=1.01GB, used=1000.00MB
System, DUP: total=8.00MB, used=4.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=1.00GB, used=1.41MB
Metadata: total=8.00MB, used=0.00

# dd if=/mnt/backupWin/iscsi/iscsiSBS of=/mnt/tmp/1 bs=100M count=90
dd: writing `/mnt/tmp/1': No space left on device
82+0 records in
81+0 records out
8560574464 bytes (8.6 GB) copied, 280.973 s, 30.5 MB/s

# btrfs filesystem df /mnt/tmp/
Data: total=7.97GB, used=7.97GB
System, DUP: total=8.00MB, used=4.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=1.00GB, used=11.39MB
Metadata: total=8.00MB, used=0.00

# rm /mnt/tmp/1 
# btrfs filesystem df /mnt/tmp/
Data: total=7.97GB, used=5.65GB
System, DUP: total=8.00MB, used=4.00KB
System: total=4.00MB, used=0.00
Metadata, DUP: total=1.00GB, used=8.06MB
Metadata: total=8.00MB, used=0.00


 
 Ben.

Libor

signature.asc
Description: This is a digitally signed message part.

Bug#684364: target: reports vfs_writev() returned -28 on iscsi activity

[Libor Klepáč]

Hello, i have just noticed oops, which happend during experiments this morning

Libor

[141443.054425] btrfs: block rsv returned -28
[141443.054428] [ cut here ]
[141443.054466] WARNING: at /build/buildd-linux_3.2.21-3-amd64-
l_qIBB/linux-3.2.21/fs/btrfs/extent-tree.c:5985 
btrfs_alloc_free_block+0xd7/0x284 [btrfs]()
[141443.054470] Hardware name: VMware Virtual Platform
[141443.054472] Modules linked in: autofs4 tcm_loop tcm_fc iscsi_target_mod 
target_core_pscsi target_core_file target_core_iblock target_core_mod 
des_generic ecb md4 hmac nls_utf8 cifs libfc scsi_transport_fc scsi_tgt 
configfs vmsync(O) vmhgfs(O) nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc 
dm_multipath scsi_dh loop coretemp crc32c_intel ghash_clmulni_intel 
aesni_intel aes_x86_64 parport_pc joydev parport usbhid snd_pcm snd_page_alloc 
snd_timer snd vmw_balloon soundcore hid aes_generic cryptd psmouse serio_raw 
pcspkr processor ac evdev power_supply thermal_sys i2c_piix4 i2c_core 
container shpchp vmci(O) button ext4 crc16 jbd2 mbcache btrfs crc32c libcrc32c 
zlib_deflate dm_mod sr_mod cdrom ata_generic sd_mod crc_t10dif uhci_hcd floppy 
ehci_hcd usbcore usb_common e1000 ata_piix mptspi scsi_transport_spi mptscsih 
mptbase libata scsi_mod [last unloaded: autofs4]
[141443.054526] Pid: 28983, comm: btrfs-transacti Tainted: G   O 
3.2.0-3-amd64 #1
[141443.054529] Call Trace:
[141443.054537]  [81046901] ? warn_slowpath_common+0x78/0x8c
[141443.054550]  [a01441fe] ? btrfs_alloc_free_block+0xd7/0x284 
[btrfs]
[141443.054566]  [a01690fe] ? read_extent_buffer+0x94/0xed [btrfs]
[141443.054575]  [a01377bf] ? __btrfs_cow_block+0x102/0x33a [btrfs]
[141443.054585]  [a0137aee] ? btrfs_cow_block+0xf7/0x143 [btrfs]
[141443.054595]  [a013a546] ? btrfs_search_slot+0x225/0x64e [btrfs]
[141443.054608]  [a0148750] ? btrfs_del_csums+0xc8/0x252 [btrfs]
[141443.054618]  [a013ff9c] ? __btrfs_free_extent+0x54f/0x5c8 [btrfs]
[141443.054630]  [a0142fc9] ? run_clustered_refs+0x65e/0x6aa [btrfs]
[141443.054642]  [a01430de] ? btrfs_run_delayed_refs+0xc9/0x176 
[btrfs]
[141443.054647]  [8134a0a0] ? mutex_lock+0xd/0x2d
[141443.054661]  [a0150153] ? btrfs_commit_transaction+0x8f/0x6f9 
[btrfs]
[141443.054667]  [8105f5f3] ? add_wait_queue+0x3c/0x3c
[141443.054679]  [a014faba] ? join_transaction.isra.24+0x5a/0x1f3 
[btrfs]
[141443.054692]  [a0150bd5] ? start_transaction+0x1ed/0x242 [btrfs]
[141443.054705]  [a014a7ad] ? transaction_kthread+0x156/0x20f [btrfs]
[141443.054717]  [a014a657] ? btrfs_congested_fn+0x7b/0x7b [btrfs]
[141443.054720]  [8105efad] ? kthread+0x76/0x7e
[141443.054725]  [81351cf4] ? kernel_thread_helper+0x4/0x10
[141443.054729]  [8105ef37] ? kthread_worker_fn+0x139/0x139
[141443.054732]  [81351cf0] ? gs_change+0x13/0x13
[141443.054734] ---[ end trace 2684d70a838e2d6c ]---

signature.asc
Description: This is a digitally signed message part.

Bug#646703: open-vm-tools: Vmmemctl on squeeze

[Libor Klepáč]

Package: open-vm-tools
Version: 1:2011.08.21-471295-3
Severity: wishlist

Hi,
i'm backporting open-vm-tools to squeeze to use on our servers.
When backporting some last release (which where not in debian archive), I 
noticed, that init script is complaining about missing vmmemctl.
When i backported 2:8.8.0+2011.09.23-491607-1 from sid, i noticed this message 
is gone.
But it seems that module is still missing. In newer kernel there is 
vmw_balloon.ko, which probably replaces this.
But in 2.6.32, there is no such module.
Is there a way to provide some vmmmectl for squeeze?

With regards
Libor Klepac


-- System Information:
Debian Release: 6.0.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages open-vm-tools depends on:
ii  libc6 2.11.2-10  Embedded GNU C Library: Shared lib
ii  libdumbnet1   1.12-3+b1  A dumb, portable networking librar
ii  libfuse2  2.8.4-1.1  Filesystem in USErspace library
ii  libgcc1   1:4.4.5-8  GCC support library
ii  libglib2.0-0  2.24.2-1   The GLib library of C routines
ii  libicu44  4.4.1-7International Components for Unico
ii  libstdc++64.4.5-8The GNU Standard C++ Library v3
ii  procps1:3.2.8-9  /proc file system utilities

Versions of packages open-vm-tools recommends:
ii  ethto 1:2.6.34-3 display or change Ethernet device 
ii  open- 2:8.8.0+2011.09.23-491607-1~bcom+1 Source for VMware guest systems dr
pn  zerof none (no description available)

Versions of packages open-vm-tools suggests:
pn  open-vm-toolbox   none (no description available)

-- Configuration Files:
/etc/vmware-tools/tools.conf changed:


-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#642201: trac-tags: Please fix README.Debian

[Libor Klepáč]

Package: trac-tags
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
i have installed package trac-tags and enabled in trac.ini according to 
README.Debian.
But trac-admin . upgrade didn't work.
This page http://trac-hacks.org/wiki/TagsPlugin states different installation 
instructions.
In [components] there should be
tractags.* = enabled

and in [tags] , ticket_field should contain keywords instead of keyword

With regards
Libor

- -- System Information:
Debian Release: wheezy/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJOeGDqAAoJEPDvjG7Cn0eONPgP/3brR8q0HtPXQfsVRm+Hsuwp
L4Nnhz2uJHZEmArR7JyGf4HF8CSTZAOk9+wSI/b2vCdCJMk41EmqecqEyZaaDDkx
7ATZmaAA+s2sVSvsBekUqDFYcOUZvPCsWJJqoZGY5rK9fvUAXj4x6Fceauc7lWfi
mO1hDPMRco2wBQTZ911qBcvIWGQ3ufvutBxrrmfcpu21r5HmEF9pdjJ7GWI4DbII
Xz5cQDSZovCK9acnwP+kVjAFpTRYZkGxBbCpoX2hLbdf+CDKV8VGwFVS+a0Nf6oW
osIb5qQuKUCj8ALmG85/IgWBT3ce48HoDpssLrmhJ5VpjX6IuKuu/am+G0YemS5u
sVFMP/pe3kLrcOlA2l1coeQ41wtr7KUd4l7fdzh01RrVhDTj8L/u8QZ934EJ1vGs
P5OwAnHDRXtH17iqVRvDkEFc+KrzxexqkAZrjDQMLtsIFgpjcO6M5xGmQbovQ/oy
ET8nsmJ9+MJOOSUG7/yOFSH7q/v9bX11U4vuR1qMvP7HUR7ss9+gc9Hrk1Xfzo2q
Y9QzbILSGjwX/xVk7FB3XmcRTCZz4OMBxRIFXUqHeu81dc2SeYPVKx89Z5XLdIAS
dqW34su7sMVMqvIvfYvlL8FsaX4dMgKH0sJvRrW/ScldqKgZdlhLENS210oyVPo3
+C7Om843Djw4TIfP0rZe
=YMk1
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#596972: archdetect: netboot amd64 writes that LIBDI_4.7 not found

[Libor Klepáč]

Hi,
i installed new package debian-installer-6.0-netboot-amd64 and installer works 
fine now
.
I also switched from using mirror ftp.cz.debian.org, which has dns record of 
ftp.hr.debian.org mirror, maybe this mirror is somehow broken?
Where can i report this dns breakage?

Libor


signature.asc
Description: This is a digitally signed message part.

Bug#596972: archdetect: netboot amd64 writes that LIBDI_4.7 not found

[Libor Klepáč]

Package: archdetect
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
i'm trying to install new vmware virtual machine (esx4.1) using netboot amd64 
daily builds.

It doesn't detect disks, when i run disk-detect from shell i get
archdetect: /lib/libdebian-installer.so.4: version `LIBDI_4.7' not found 
(required by archdetect)

also network-console doesn't run, with same message.
I tried several daily builds with same result.
I have no clue what should be wrong, installing in esxi always worked fine.

Libor


- -- System Information:
Debian Release: squeeze/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-ck1-1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJMkNoDAAoJEPDvjG7Cn0eOWJEQAJHXQPfR6tv/ff/un68juvnI
TolL2OX/8FsqcgMOAF9olB4DtkEvAQuWxABOqaw+HSxhNT1bFXUpocE5cer06mTm
X+E23oOw3OBCDJBLeSujshN6cj7jzMbbJKz2RZ1KRpzDuYUvV0HGG/pRbK2tEAXp
7ERqc23+guCURPWopLoz7UcHzTuIxs1GVXQVjraj+skKgkxFjzOpOWN8WfYzSTiu
UZreOUHz1/hHEsGl+IFra4GLA9lowFLkhJr/hMeZw0vPm+SuvZPWbVdkr6Xe06Jg
gvYRedcN1vSnhlQFCscWYRxVPWz0oomd3/xnTjm1w81dIwJwlV/s5be6pIt2yj+N
oslntFwknJ1PlQOPsWmSnH3NNbne2qK2XXiopv2Gf36cyji+N5ef4+NGH+Byk4t9
PbXll1EPctUUIfOVzthGkKauf90BDzLx7S/++gP1K2OYIZQolMl6LFrqyL2OcznH
N/EOKyM76Y6ubmbLE+3XKdYzRAVdqhTUS6CCE1bE6v7ul7Anm6sFwXp1oovjSjbL
5ATQalWmlWm+nIKsdmk2yTtCyetr9f8DTc1LknOhMnwfhEdh5urZMPaITyDDdgr/
wp16qXFOmjhdk/XGR+IpTYEtU6aOifLneTuhkDpPsUxFHVl+UT7XKq2UjMHipbrR
lyZo/Js+o2vxQCAAhkPF
=u53v
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#595729: auto.smb in autofs5 missing support for mounting with credentials

[Libor Klepáč]

Package: autofs5
Version: 5.0.4-3.1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi
after installing autofs5 to new hosts, i noticed, that creating file 
/etc/auto.smb.ip.address
with credentials has no effect on mounting shares.
There is no parsing in auto.smb, like it was in autofs4.

Thanks,
Libor


- -- System Information:
Debian Release: squeeze/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.35-ck1-1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages autofs5 depends on:
ii  libc62.11.2-5Embedded GNU C Library: Shared lib
ii  ucf  3.0025+nmu1 Update Configuration File: preserv

Versions of packages autofs5 recommends:
ii  module-init-tools 3.12-1 tools for managing Linux kernel mo
ii  nfs-common1:1.2.2-4  NFS support files common to client

autofs5 suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJMhKRmAAoJEPDvjG7Cn0eOlIAP/2EfGQGOxSofKBwRQ4yTDcaV
/vy3YteqgH5CcAUxlseHfCNuzn0w7ZCCs0DoahyO34iHr7zqnSelZxpDb9PvGSRi
IKMTLcE1fybvZmqvIJTsFX482fylWrYmbb8zF9/hA9K+ZFKW1yhAzrvW7ruiNJDD
3gUIb0C5DUfsVCqek4ewJKfQOVz0x2zgvwrISB9oyjx8FMcoerJcknmX5kpVDpyu
FYSI8BMv4XaSgKxZ4RLh3qqODfPcGZjiFrz5twHQ16ZvuDOpyE2v95wvUwSxm7t3
wQ1Kh5tpzanN2SRTPc074mTg5HR4SyLyR6CYVJjqxAuvZT59F5PNrT+ZKpeK2GMu
gpzuCuOkdJeuUH3jl1D7ZVUs5e46U+tV9btCdXzB8yDSfU7SNm+g8lcf/6JRnWrw
Shn30SEygI/NVA2CAoQi4Ig/x5NnHZeNWC8xGUwthg04n3jzJ3WMtrrIaRNHJhUZ
n563MAjqjrSk7e30cPq3kdJUVPSkZzR8wm2+v/cDJtC1s4jdaeU3iL3Q43iiNEJH
HdC9gPbE1TUf1WoL0AvvsY7pbfKu4LKnxJR3qMMvz2wyNnKTNRua29ZlxtqLpOAr
YUIda5yuU09Zx+2O2D/4n4+1Gitu9JYU1FdwMQCFaX3F/RA9eNlCcEGZYASEh0cF
kJQJoiUeq/RmfPvW+7Xt
=oFCa
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#576646: Start cryptsetup-early after nbd-client

[Libor Klepáč]

Package: cryptsetup
Version: 2:1.1.0~rc2-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,
I didn't want to fill a bug, I just asked in mailing list but it's not read 
maybe.
Here is my message.

- --
Hi,
I don't want to fill bug, I just want to ask.

We are setting up backup server, which will boot from nfs (this works, nfsroot 
created easily using debootstrap). Four local disks will be in raid5 (we are 
testing it in vmware now, so only one disk).

I have created luks on /dev/sda , then created lvm on top of it.

This host has to boot automatically and we dont want to have keyfile on 
filesystem of it. So i started nbd-server on other host and put key into it 
(1024B).
So on backup server crypttab looks like this
backup  /dev/sda   /dev/nbd0luks,size=8192,noearly

Problem is that /etc/init.d/cryptdisks starts after lvm, so i put 
/etc/init.d/lvm2 start to rc.local.

nbd-client has to start before cryptdisks, so I added nbd-client to 
Required-Start field of cryptdisk. (And i have had to remove X-Start-Before:   
 checkfs so it doesn't complain about loop)

When i try to add nbd-client to cryptdisks-early (so luks is opened before lvm 
starts), insserv complains about loop. I don't know how to solve this, do you 
have any ideas please?

insserv -v -d
insserv: There is a loop between service cryptdisks-early and nbd-client if 
started
insserv:  loop involving service nbd-client at depth 7
insserv:  loop involving service networking at depth 6
insserv: There is a loop between service cryptdisks-early and nbd-client if 
started
insserv:  loop involving service lvm2 at depth 3
insserv:  loop involving service cryptdisks-early at depth 2
insserv:  loop involving service udev at depth 1
insserv:  loop involving service mountnfs at depth 10
insserv: There is a loop between service lvm2 and cryptdisks-early if started
insserv:  loop involving service checkfs at depth 16
insserv: exiting now without changing boot order!

Any ideas please? Or is this setup just to complicated/wrong?
- -

We are starting crypted as nonearly now , and we are starting lvm in rc.local 
now - no problem for us.

This wishlist is just to let you know about the loop.
It would be nice if there is some solution for this, maybe our setup is to 
insane to support ;)

With regards
Libor

- -- System Information:
Debian Release: squeeze/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bfs311-bfs311 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLuudFAAoJEPDvjG7Cn0eOSF8P/jDFQ16zrUsLyGI2xtqM6dcb
jvtpkZuOjWaXiTAT/lZ6JHDXWXtptAkTH6JJEneY+JGFhLy5OM8mEyfdJ6ljat9D
RnDujx2xjfMBRGGKCY+iQ/yQUgFoUaZTh/WBlGkwdsAnHKAMZW5H4gYDzhpRT212
VB5pywuDLkMXsLJhc/XVnwZsoJj0yMX5NVfLAuA/xqBU/E180fBeQDqoELEPSNC6
8nvO4si3aIvtN+maR8QxOQXnkjnEofG8qpvZ5Tuk++VWpoQe+8fSUFzw6/eCNH+t
iZ1tj4Lsn9iZYGxIN8x+rWLA2RNIqUVzfuzaxWX3tEyCpCvNU0KrRy9Hf4fv+LW2
PODjAtCiCM2JdAFq7hFgrnkl2MxPgj6d1SYtVhsI4hDt5IukPn+fRj/pC7R8tfaR
Kt/viLPhfsPvkZouk8RwbW2IwiM4moss2SboehkuZsw3gUC9NjH9hgBxED+MFOe5
GWYBTgQTSgjcs46U0XdNAWSTsqvyRRR3KUc1KyyyJcWktbsKQ3jNVaIXAxSgMd5O
0syE9NbB0iwsQOnd99MCcgEkGXyaSN76SCWtm22/nCSuHNFpz2s7Ry6NAfs1TANe
tztXqEKOpWMKaZKLRlg82xeUN5UHtZWq9hKsZ2ZYIDyY8ALErPDBHqXbKbb7Qp1f
qjUoNqTC/+jGFEXWhsT3
=PidW
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#568498: mysql-server-5.1: Unable to backup db with '-' in name with mysqlhotcopy

[Libor Klepáč]

Package: mysql-server-5.1
Version: 5.1.43-1
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
I have upgraded mysql from 5.0.84? to 5.1.43 today and now, I'm unable to 
backup databases with - in name using mysqlhotcopy.
For example db named test-test is now saved in directory 
/var/lib/mysql/t...@002dtest
Running 
/usr/bin/mysqlhotcopy test-test /tmp/x/nAgJGLdC
results in
Cannot open dir '/var/lib/mysql/test-test': No such file or directory at 
/usr/bin/mysqlhotcopy line 289.

Running
/usr/bin/mysqlhotcopy t...@002dtest /tmp/x/nAgJGLdC
results in
Unable to retrieve list of tables in t...@002dtest: DBD::mysql::db 
selectall_arrayref failed: Unknown database 't...@002dtest' at 
/usr/bin/mysqlhotcopy line 775.
No tables to hot-copy at /usr/bin/mysqlhotcopy line 380.

Is there some solution?

With regards
Libor


- -- System Information:
Debian Release: squeeze/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bfs311-bfs311 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mysql-server-5.1 depends on:
ii  adduser 3.112add and remove users and groups
ii  debconf [debconf-2.0]   1.5.28   Debian configuration management sy
ii  libc6   2.10.2-5 Embedded GNU C Library: Shared lib
ii  libdbi-perl 1.609-1  Perl Database Interface (DBI)
ii  libgcc1 1:4.5-20100202-1 GCC support library
ii  libmysqlclient165.1.43-1 MySQL database client library
ii  libstdc++6  4.5-20100202-1   The GNU Standard C++ Library v3
ii  libwrap07.6.q-18 Wietse Venema's TCP wrappers libra
ii  lsb-base3.2-23   Linux Standard Base 3.2 init scrip
ii  mysql-client-5.15.1.43-1 MySQL database client binaries
ii  mysql-common5.1.43-1 MySQL database common files (e.g. 
ii  passwd  1:4.1.4.2-1  change and administer password and
ii  perl5.10.1-10Larry Wall's Practical Extraction 
ii  psmisc  22.10-1  utilities that use the proc file s
ii  zlib1g  1:1.2.3.5.dfsg-1 compression library - runtime

Versions of packages mysql-server-5.1 recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20090911cvs-2 simple mail user agent
ii  libhtml-template-p 2.9-1 HTML::Template : A module for usin

Versions of packages mysql-server-5.1 suggests:
pn  tinycanone (no description available)

- -- debconf information:
  mysql-server-5.1/postrm_remove_databases: false
  mysql-server-5.1/really_downgrade: false
  mysql-server/error_setting_password:
  mysql-server-5.1/start_on_boot: true
  mysql-server-5.1/nis_warning:
  mysql-server/password_mismatch:
  mysql-server/no_upgrade_when_using_ndb:

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAktrzowACgkQhMrxGRe1HmGewACeIdfeuhrulr2fa0vkARvV3cRl
qPIAoJLhx+5KiNRlU631W5PLsvlzMuvA
=NvPg
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#565971: nslcd: Please add apache2 to X-Start-Before in initscript

[Libor Klepáč]

Package: nslcd
Version: 0.7.2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
we are using libnss-ldapd on machine where we also run apache, using 
apache2-mpm-itk - ie. version where each virtual may run under different user.
It looks like this
VirtualHost x.x.x.x:80
ServerAdmin webmas...@localhost
ServerName server

AssignUserID user www-data
/VirtualHost

As you can see, user/group needs to be resolved to uid/gid (uid only in our 
setup), so nslcd should run before apache.

Thanks,

Libor


- -- System Information:
Debian Release: squeeze/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-bfs311-bfs311 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAktWxaMACgkQhMrxGRe1HmHnAwCgqTzyrJ8EjTpvI38iZO2j1AxI
HOkAnjG564G//mfz7eCBE3pypB2KtK5g
=BWxK
-END PGP SIGNATURE-



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#554162: fail2ban: sometimes(frequently) fails to load iptable rules with multiple jails

[Libor Klepáč]

Hi,
sorry for late answer.
I have removed action.py patch and put 

sleep ${RANDOM:0:1}.${RANDOM: -1:1}

onto first line of actionstart and actionstop
So I get more sleep values without big delay - it should be from 0.0 to 3.9, I 
think

It seems to work nicely now


With regards
Libor

Dne čtvrtek 05 Listopad 2009 16:17:13 Yaroslav Halchenko napsal(a):
 oki doki... it is indeed the fact here -- whenever multiple
 processes/threads/whatever  contact iptables in parallel
 
 $ for f in {1..5}; do cn=fail2ban-proftpd$f; echo $cn; /bin/sh -c
  iptables -N $cn; iptables -A $cn -j RETURN; iptables -I INPUT -p tcp -m
  multiport --dports ftp,ftp-data,ftps,ftps-data -j $cn ; done
  fail2ban-proftpd1
 fail2ban-proftpd2
 fail2ban-proftpd3
 fail2ban-proftpd4
 fail2ban-proftpd5
 $ for f in {1..5}; do cn=fail2ban-proftpd$f; echo $cn; iptables -D INPUT
  -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data -j $cn; iptables
  -F $cn; iptables -X $cn; done fail2ban-proftpd1
 fail2ban-proftpd2
 fail2ban-proftpd3
 fail2ban-proftpd4
 fail2ban-proftpd5
 
 So -- everything was cool, lets try now start them in parallel:
 
 $ for f in {1..5}; do cn=fail2ban-proftpd$f; echo $cn; /bin/sh -c
  iptables -N $cn; iptables -A $cn -j RETURN; iptables -I INPUT -p tcp -m
  multiport --dports ftp,ftp-data,ftps,ftps-data -j $cn  ; done
  fail2ban-proftpd1
 [2] 7312
 fail2ban-proftpd2
 [3] 7314
 fail2ban-proftpd3
 [4] 7315
 fail2ban-proftpd4
 [5] 7322
 fail2ban-proftpd5
 iptables: Invalid argument. Run `dmesg' for more information.
 iptables: Resource temporarily unavailable.
 $
 $ for f in {1..5}; do cn=fail2ban-proftpd$f; echo $cn; iptables -D INPUT
  -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data -j $cn; iptables
  -F $cn; iptables -X $cn; done fail2ban-proftpd1
 fail2ban-proftpd2
 fail2ban-proftpd3
 iptables: No chain/target/match by that name.
 fail2ban-proftpd4
 fail2ban-proftpd5
 
 So, here we got it -- iptables might not digest nicely a bulk of requests
  done in parallel.  Even if I set affinity for children tasks to run on the
  same core with taskset (so there could not be real parallelism) -- same
  shit.
 
 You get more fun if you go beyond 5 ;) (all those missing .so etc messages)
 
 BTW -- there were no further information in dmesg
 
 So, as a temporary solution I would just advise you to add arbitrary sleep
  time at the beginning of each chain initiation/shutdown(just in case),
  smth like:
 
 actionstart = sleep ${RANDOM:0:1}
   iptables -N fail2ban-name
   iptables -A fail2ban-name -j RETURN
   iptables -I INPUT -p protocol -m multiport --dports port
  -j fail2ban-name
 
 actionstop = sleep ${RANDOM:0:1}
  iptables -D INPUT -p protocol -m multiport --dports port
  -j fail2ban-name iptables -F fail2ban-name
  iptables -X fail2ban-name
 
 
 I guess average delay of 5 sec would be tolerable, right? ;)
 if you have better sleep then use 0.${RANDOM:0:1} ;-)
 
 On Thu, 05 Nov 2009, Libor Klepáč wrote:
  Hi,
  You are welcome.
  Let's see if someone else can confirm this behaviour. Maybe they will
  have other ideas.
 


signature.asc
Description: This is a digitally signed message part.

Bug#554162: fail2ban: sometimes(frequently) fails to load iptable rules with multiple jails

[Libor Klepáč]

Hi,
I have done some testing without the patch
I have tested 
 - putting sleep between commands (I have tested this yesterday too) - it 
didn't help
 - putting all commands in one line, separated with ; - it didn't help
 - putting all commands in one line, separated with   - it didn't help
 - putting all commands in one line, separated with ; and I put () around 
whole line - it failed differently, it seems, it separates commands somewhere 
on it's own
-
sh: -c: line 1: syntax error: unexpected end of file

2009-11-04 09:34:33,313 fail2ban.actions.action: ERROR  (iptables -N fail2ban-
postfix returned 200
-

 now the question -- what is your /bin/sh? ;)
 could you try different kernel? I've tried on 2.6.26-2-amd64

/bin/sh is bash 3.2-5

Sorry , I cannot use another kernel now, this is our main production server.

Well, I really don't know, where the problem might be, so I'll stick to this 
patch for now, it works for me.
We have some filtering of smtp port based on results from amavis and 554 from 
postfix, we have around 100-200 hosts banned in this jail (for 30 minutes) all 
day, I think it filtres lots of spam - I can send it as some wishlist bug - but 
i think it's based on some filter I have downloaded somewhere, so I don't 
remember licence


Libor


Dne úterý 03 Listopad 2009 22:09:10 Yaroslav Halchenko napsal(a):
  Patch is working, but i can't use action_mw
  (output goes like this
  ---
  2009-11-03 21:04:02,138 fail2ban.actions.action: ERROR  printf %b
  Subject: [Fail2Ban] cyrus: started
  From: Fail2Ban fail2ban
 
 well -- that is what the patch you've applied accomplished
 unfortunately :-/ since the mailing command is a multiline printf
 command.  imho instead of that patch I would simple tune up the action
 for banning -- just add sleep 1 (or sleep 0.1 if system has that recent
 sleep ;)) after each command  and see how that helps
 
 or may be alternatively just placing all commands on 1 line with ;
 between them -- so they should start as a one command (you said that
 system tolerated that fine)
 
  All commands in one line work ok from command line.
 
 interesting -- thanks for checking
 
  Sequence is also ok. Fail2ban launches actions in threads?
 
 to say the truth -- I don't know exactly... from what I know, it just
 calls system() from stdlib, which should call /bin/sh -c '.'
 
 I still think that the issue is deeper underground (iptables return
 before actually completing modification of the table etc) although
 myself could not replicate it on none of boxes (biefie enough: 8 cores,
 64GB RAM etc) with smth like
 
 for f in {1..100}; do /bin/sh -c iptables -N fail2ban-proftpd; iptables -A
  fail2ban-proftpd -j RETURN; iptables -I INPUT -p tcp -m multiport --dports
  ftp,ftp-data,ftps,ftps-data -j fail2ban-proftpd; iptables -D INPUT -p tcp
  -m multiport --dports ftp,ftp-data,ftps,ftps-data -j fail2ban-proftpd;
  iptables -F fail2ban-proftpd; iptables -X fail2ban-proftpd; done
 
 now the question -- what is your /bin/sh? ;)
 could you try different kernel? I've tried on 2.6.26-2-amd64
 


signature.asc
Description: This is a digitally signed message part.

Bug#554162: fail2ban: sometimes(frequently) fails to load iptable rules with multiple jails

[Libor Klepáč]

Hi,
there seems to be some problem with sequence of commands run from python.
Maybe our server is too powerfull? (poweredge 2950 with two 4 core processors, 
old server was some old pentium4 with ht, there were no such problems)

If i run those commands separately from command line ,there is no problem.

But if whole (multiline) actionstart is run, there seems to be problem with 
order of commands.
Problem is, that
iptables -I INPUT -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data -j 
fail2ban-proftpd
is run in time, when there is no such chain, so kernel tries to autoload 
module for it (but there is no such module) (you can try it by running this 
command)

You get this
iptables v1.4.4: Couldn't load target `fail2ban-
proftpd':/lib/xtables/libipt_fail2ban-proftpd.so: cannot open shared object 
file: No such file or directory

Patch from sf explodes actionstart by newline and launches each line 
separately (maybe with some locking? I can't read python)

With regards
Libor


Dne úterý 03 Listopad 2009 16:00:30 Yaroslav Halchenko napsal(a):
 brr... are you sure you just have some problem with iptables? what if
 whenever there is no fail2ban running you run those commands while being
 root
 
 iptables -N fail2ban-proftpd
 iptables -A fail2ban-proftpd -j RETURN
 iptables -I INPUT -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data
  -j fail2ban-proftpd
 
 will you get at some point that
 iptables v1.4.4: Couldn't load target
  `fail2ban-proftpd':/lib/xtables/libipt_fail2ban-proftpd.so: cannot open
  shared object file: No such file or directory
 
 or would be there any other error reported?
 
 On Tue, 03 Nov 2009, Libor Klepac wrote:
  Package: fail2ban
  Version: 0.8.4-1
  Severity: important
 
  Hi,
  I have problems with using several jails. It was there before, but didn't
  hit so hard as today, when i was unable to restart fail2ban cleanly , i
  was trying it for maybe 50 times (changing configs, installing python2.4
  ...etc). I seems to fail to execute iptables in correct orderd leading to
  something like this in its output
 


signature.asc
Description: This is a digitally signed message part.

Bug#554162: fail2ban: sometimes(frequently) fails to load iptable rules with multiple jails

[Libor Klepáč]

Hi,
i usually write little confusing ;)

Patch is working, but i can't use action_mw 
(output goes like this
---
2009-11-03 21:04:02,138 fail2ban.actions.action: ERROR  printf %b Subject: 
[Fail2Ban] cyrus: started
From: Fail2Ban fail2ban
To: fail2...@xxx\n
Hi,\n
The jail cyrus has been started successfully.\n
Regards,\n
Fail2Ban | /usr/sbin/sendmail -f fail2ban fail2...@xxx FAILED
/bin/sh: -c: line 0: unexpected EOF while looking for matching `'
/bin/sh: -c: line 1: syntax error: unexpected end of file
2009-11-03 21:04:02,142 fail2ban.actions.action: ERROR  printf %b Hi,\n 
returned 200
/bin/sh: The: command not found
2009-11-03 21:04:02,145 fail2ban.actions.action: ERROR  The jail http has been 
started successfully.\n returned 7f00
/bin/sh: Regards,n: command not found
2009-11-03 21:04:02,148 fail2ban.actions.action: ERROR  Regards,\n returned 
7f00
/bin/sh: -c: line 0: unexpected EOF while looking for matching `'
/bin/sh: -c: line 1: syntax error: unexpected end of file
2009-11-03 21:04:02,151 fail2ban.actions.action: ERROR  Fail2Ban|mail -s 
[Fail2Ban] http: started fail2...@xxx returned 200
2009-11-03 21:04:03,152 fail2ban.actions.action: ERROR  printf %b Hi,\n
The jail http has been started successfully.\n
Regards,\n
Fail2Ban|mail -s [Fail2Ban] http: started fail2...@xxx FAILED
---

All commands in one line work ok from command line.

I tried little python script
--
import os

realCmd = echo 1\necho 2\necho 3\necho 11\necho 12\necho 13\necho 21\necho 
22\necho 23\necho 31\necho 32\necho 33
retcode = os.system(realCmd)
--

Sequence is also ok. Fail2ban launches actions in threads?

Libor



Dne úterý 03 Listopad 2009 20:14:07 Yaroslav Halchenko napsal(a):
 d'oh me -- I've read your original incorrectly (that you applied patch
 and it didn't help ;-)) .
 
 Just out of research -- could you please run in shell all 3 commands
 in a single line like
 
 iptables -N fail2ban-proftpd; iptables -A fail2ban-proftpd -j RETURN;
  iptables -I INPUT -p tcp -m multiport --dports ftp,ftp-data,ftps,ftps-data
  -j fail2ban-proftpd
 
 I would really not expect some out of order execution from Python's
 os.system and it might be that real problem is buried deeper.
 
 On Tue, 03 Nov 2009, Libor Klepáč wrote:
  Hi,
  there seems to be some problem with sequence of commands run from python.
  Maybe our server is too powerfull? (poweredge 2950 with two 4 core
  processors, old server was some old pentium4 with ht, there were no such
  problems)
 
  If i run those commands separately from command line ,there is no
  problem.
 
  But if whole (multiline) actionstart is run, there seems to be problem
  with order of commands.
  Problem is, that
  iptables -I INPUT -p tcp -m multiport --dports
  ftp,ftp-data,ftps,ftps-data -j fail2ban-proftpd
  is run in time, when there is no such chain, so kernel tries to autoload
  module for it (but there is no such module) (you can try it by running
  this command)
 


signature.asc
Description: This is a digitally signed message part.

Bug#539898: ltsp-server: ltsp-build-client fails to build i386 client on amd64

[Libor Klepáč]

Hi 
I have just upgraded to 5.1.81-1 and i can still see those read-only messages 
during boot - X shows up, but i'm unable to type to login field, mouse is also 
dead (both usb), ps2 keyboard doesn't type either
it was the same with 5.1.79-2 i think
i was testing i386 client only

Libor

Dne středa 05 Srpen 2009 22:45:48 Vagrant Cascadian napsal(a):
 On Tue, Aug 04, 2009 at 05:55:59PM +0200, Libor Klepáč wrote:
  there is  missing in second elif in patch
  It aplies cleanly for me and i386 client is building now.

 oops. thanks for noticing! really fixed upstream, now.

  It's build, but it has some problems with booting (it's the same with
  amd64 env.) - it cannot write on read-only system - maybe 5.1.79-2 fixes
  this?

 yes, that was an issue i tried to fix in 5.1.79-2. it had to do with dash
 being the new default /bin/sh.

 live well,
   vagrant


signature.asc
Description: This is a digitally signed message part.

Bug#539898: ltsp-server: ltsp-build-client fails to build i386 client on amd64

[Libor Klepáč]

Package: ltsp-server
Version: 5.1.79-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,
I wanted to test new ltsp with pulseaudio fixed.
Unfortunately, build-client fails to build i386  version of boot, amd64 version 
builds ok
It dies on
cp: omitting directory `/usr/bin/'
error: LTSP client installation ended abnormally

I also tried to install chroot with debootstrap and it's ok
Log files attached

With regards
Libor


- -- Package-specific info:
packages in chroot: /opt/ltsp/amd64
ii  ldm  2:2.0.42-1   LTSP display manager
ii  ltsp-client  5.1.79-1 LTSP client environment
ii  ltsp-client-core 5.1.79-1 LTSP client environment
ii  ltspfsd  0.5.13-1 Fuse based remote 
filesystem daemon for LTSP thin clients
ii  ltspfsd-core 0.5.13-1 Fuse based remote 
filesystem daemon for LTSP thin clients
lts.conf from chroot: /opt/ltsp/amd64
# This is the default lts.conf file for ltsp 5.
# For more information about valid options please see: 
# /usr/share/doc/ltsp-client-core/lts-parameters.txt.gz
# in the client environment or
# /usr/share/doc/ltsp-server/lts-parameters.txt.gz
# on the server

[default] 
LTSP_CONFIG=True
#SOUND=False
#LOCALDEV=False
#CONFIGURE_X=False

- -- System Information:
Debian Release: squeeze/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ltsp-server depends on:
ii  debconf [debconf-2.0] 1.5.27 Debian configuration management sy
ii  debconf-utils 1.5.27 debconf utilities
ii  debootstrap   1.0.15 Bootstrap a basic Debian system
ii  gettext-base  0.17-6 GNU Internationalization utilities
ii  iproute   20090324-1 networking and traffic control too
ii  lsb-release   3.2-23 Linux Standard Base version report
ii  openssh-client1:5.1p1-7  secure shell client, an rlogin/rsh
ii  python2.5.4-3An interactive high-level object-o
ii  tcpd  7.6.q-18   Wietse Venema's TCP wrapper utilit
ii  update-inetd  4.31   inetd configuration file updater

Versions of packages ltsp-server recommends:
ii  nbd-server1:2.9.13-2 Network Block Device protocol - se
ii  nfs-kernel-server 1:1.2.0-2  support for NFS kernel server
pn  openbsd-inetd | inet-superser none (no description available)
ii  openssh-server1:5.1p1-7  secure shell server, an rshd repla
ii  squashfs-tools1:4.0-1Tool to create and append to squas
ii  tftpd-hpa 5.0-3  HPA's tftp server

Versions of packages ltsp-server suggests:
pn  audi none  (no description available)
pn  dhcp none  (no description available)
ii  esou 0.2.41-5Enlightened Sound Daemon - clients
ii  kde- 4:4.2.96-1  the KDE 4 window manager (KWin)
pn  ldm- none  (no description available)
ii  liba 1.0.20-1ALSA library additional plugins
ii  ltsp 0.5.13-1Fuse based remote filesystem for L
ii  nas- 1.9.2-1 Network Audio System - client bina
ii  open 3.4.7.2-4   standards compliant, fast, light-w
ii  puls 0.9.16~test2~20090726git59659e1db-1 PulseAudio ESD compatibility layer
pn  sdm  none  (no description available)
ii  xaut 1:1.0.3-2   X authentication utility

- -- debconf information:
  ltsp-server/build_client: false

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkp4B/4ACgkQhMrxGRe1HmH7EgCfT+EieJTiCXB30y4UMpOCQN3E
1Y4AoJ7bZ7sMDr9ZJOwoTzux75zh2mTD
=0Z37
-END PGP SIGNATURE-
DEBUG: Loading plugin: install: /usr/share/ltsp/plugins/ltsp-builI: Retrieving 
Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 150C8614919D8446E01E83AF9AA38DCD55BE302B)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Found additional required dependencies: dash insserv libdb4.7 
I: Found additional base dependencies: libgcrypt11 libgpg-error0 
I: Checking component main on http://192.168.0.3:/debian...
I: Retrieving adduser
I: Validating adduser
I: Retrieving apt
I: Validating apt
I: Retrieving base-files
I: Validating base-files
I: Retrieving base-passwd
I: Validating base-passwd
I: Retrieving bash
I: Validating bash
I: Retrieving bsdmainutils

Bug#539898: ltsp-server: ltsp-build-client fails to build i386 client on amd64

[Libor Klepáč]

Hi,
there is  missing in second elif in patch
It aplies cleanly for me and i386 client is building now.

It's build, but it has some problems with booting (it's the same with amd64 
env.) - it cannot write on read-only system - maybe 5.1.79-2 fixes this?

With regards
Libor

Dne úterý 04 Srpen 2009 16:27:34 Vagrant Cascadian napsal(a):
 tags 539898 pending
 thanks

 On Tue, Aug 04, 2009 at 12:05:54PM +0200, Libor Klepáč wrote:
  Unfortunately, build-client fails to build i386  version of boot, amd64
  version builds ok It dies on
  cp: omitting directory `/usr/bin/'
  error: LTSP client installation ended abnormally

 ah, this is a bug introduced by the new cross-architecture code (which is
 *should* be un-used for i386 on amd64 servers)...

 fixed upstream, and will include it in the next upload (although it just
 missed the 5.1.79-2 upload i made half an hour ago, unfortunately).

 this patch should fix the issue, please test it (i am unable to test it
 myself):

 === modified file 'server/plugins/ltsp-build-client/Debian/002-cross-arch'
 --- server/plugins/ltsp-build-client/Debian/002-cross-arch  2009-07-29
 16:12:13 + +++ server/plugins/ltsp-build-client/Debian/002-cross-arch  
2009-08-04 13:28:08 + @@ -23,11 +23,16 @@
  *) echo WARNING: unknown cross-architecture combination:
 $ARCH on $HOST_ARCH ;;
  esac
 -if [ -x /usr/bin/${CROSS_ARCH_EMULATOR}-static ]; then
 +if [ -z $CROSS_ARCH_EMULATOR ]; then
 +: # no cross-architecture emulator detected
 +elif [ -x /usr/bin/${CROSS_ARCH_EMULATOR}-static ]; then
  # prefer static variants
 
 CROSS_ARCH_EMULATOR=/usr/bin/${CROSS_ARCH_EMULATOR}-static +   
 elif [ -x /usr/bin/${CROSS_ARCH_EMULATOR} ]; then
 +CROSS_ARCH_EMULATOR=/usr/bin/${CROSS_ARCH_EMULATOR}
  else
 -CROSS_ARCH_EMULATOR=/usr/bin/${CROSS_ARCH_EMULATOR}
 +echo WARNING: unable to find: $CROSS_ARCH_EMULATOR in
 /usr/bin +unset CROSS_ARCH_EMULATOR
  fi
  fi
  if [ -n $CROSS_ARCH_EMULATOR ]  [ ! -x $CROSS_ARCH_EMULATOR
 ]; then

 live well,
   vagrant


signature.asc
Description: This is a digitally signed message part.

Bug#539141: earcandy: Please depend on python-wnck

[Libor Klepáč]

Package: earcandy
Version: 0.5-1
Severity: grave
Justification: renders package unusable

Hi,
i have installed this package, but it doesn't run until I installed package 
python-wnck.


~:earcandy
Traceback (most recent call last):  
   
  File /usr/bin/earcandy, line 17, in module
   
import ear_candy
   
  File /usr/share/earcandy/ear_candy/ear_candy.py, line 20, in module   
   
import wnck 
   
ImportError: No module named wnck


Please depend on it

With regards
Libor


-- System Information:
Debian Release: squeeze/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages earcandy depends on:
ii  puls 0.9.16~test2~20090726git59659e1db-1 PulseAudio sound server
ii  pyth 2.5.4-3 An interactive high-level object-o
ii  pyth 0.83.0-1simple interprocess messaging syst
ii  pyth 2.14.1-3GTK+ bindings: Glade support
ii  pyth 0.1.1-2+b1  Python bindings for libnotify
ii  pyth 1.0.3   automated rebuilding support for P

earcandy recommends no packages.

earcandy suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#530592: initramfs-tools: Same problem here

[Libor Klepáč]

Package: initramfs-tools
Version: 0.93.2
Severity: normal

Hi,
same problem here with grub2  lvm  linux-2.6.29 (system is reiserfs partition 
on lvm)
I was rebooting my notebook(because of hard freeze) after several weeks or 
months using suspend2ram.
It couldn't find /dev/disk/by-uuid/SOMEUUID, so I changed root to 
ROOT=/dev/mapper/disk--sda-system and booting now works.
After bootup, I uncommented GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub 
and run update-grub, grub.conf is now without UUIDs.

With regards
Libor

-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.29-1-amd64 root=/dev/mapper/disk--sda-system ro 
acpi_irq_balance quiet rootdelay=20

-- /proc/filesystems
reiserfs
fuseblk
ext3
xfs

-- lsmod
Module  Size  Used by
nvidia   8107304  34 
xt_tcpudp   3296  1 
iptable_nat 6176  1 
nf_nat 19972  1 iptable_nat
nf_conntrack_ipv4  14664  3 iptable_nat,nf_nat
nf_conntrack   70048  3 iptable_nat,nf_nat,nf_conntrack_ipv4
nf_defrag_ipv4  2256  1 nf_conntrack_ipv4
xt_multiport3184  1 
iptable_filter  3744  1 
ip_tables  17024  2 iptable_nat,iptable_filter
x_tables   21800  4 xt_tcpudp,iptable_nat,xt_multiport,ip_tables
vmnet  38620  13 
vmci   48200  0 
vmmon  66080  0 
binfmt_misc 9308  1 
ppdev   7528  0 
parport_pc 26744  0 
lp 10324  0 
parport37904  3 ppdev,parport_pc,lp
sco10820  2 
bridge 48048  0 
stp 2836  1 bridge
bnep   13600  2 
rfcomm 35104  4 
l2cap  19968  16 bnep,rfcomm
ipv6  283792  39 
acpi_cpufreq8192  0 
cpufreq_powersave   1760  0 
cpufreq_stats   4836  0 
cpufreq_userspace   3700  0 
cpufreq_conservative 7224  0 
microcode  25672  0 
nfsd  244992  17 
nfs   250544  0 
lockd  67924  2 nfsd,nfs
nfs_acl 3232  2 nfsd,nfs
auth_rpcgss40768  2 nfsd,nfs
sunrpc194936  15 nfsd,nfs,lockd,nfs_acl,auth_rpcgss
xfs   462336  1 
exportfs4720  2 nfsd,xfs
ext3  122528  1 
jbd50232  1 ext3
mbcache 9140  1 ext3
fuse   55200  1 
coretemp6656  0 
loop   15292  0 
firewire_sbp2  15056  0 
snd_hda_codec_realtek   243380  1 
snd_hda_codec_si3054 5088  1 
snd_hda_intel  26488  2 
snd_hda_codec  69648  3 
snd_hda_codec_realtek,snd_hda_codec_si3054,snd_hda_intel
snd_hwdep   7864  1 snd_hda_codec
snd_pcm_oss36448  0 
snd_mixer_oss  14576  1 snd_pcm_oss
snd_pcm78776  4 
snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec,snd_pcm_oss
arc42016  2 
snd_seq_dummy   3108  0 
joydev 10944  0 
ecb 3040  2 
snd_seq_oss29184  0 
snd_seq_midi6672  0 
iwlagn 80196  0 
iwlcore87712  1 iwlagn
snd_rawmidi22896  1 snd_seq_midi
snd_seq_midi_event  7504  2 snd_seq_oss,snd_seq_midi
snd_seq50800  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
rfkill 11876  2 iwlcore
btusb  12580  2 
led_class   4760  1 iwlcore
snd_timer  22240  2 snd_pcm,snd_seq
bluetooth  53860  9 sco,bnep,rfcomm,l2cap,btusb
mac80211  151576  2 iwlagn,iwlcore
i2c_i8019840  0 
snd_seq_device  7428  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
wmi 7648  0 
serio_raw   5780  0 
evdev  10496  28 
psmouse41532  0 
pcspkr  2768  0 
cfg80211   38976  3 iwlagn,iwlcore,mac80211
i2c_core   25168  2 nvidia,i2c_i801
video  19972  5 
battery 7600  0 
button  7280  0 
ac  3760  0 
snd63192  17 
snd_hda_codec_realtek,snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore   7984  1 snd
output  3328  1 video
snd_page_alloc  9776  2 snd_hda_intel,snd_pcm
reiserfs  201520  1 
dm_mirror  14016  0 
dm_region_hash 12656  1 dm_mirror
dm_log 10116  2 dm_mirror,dm_region_hash
dm_snapshot17480  0 
dm_mod 58064  8 dm_mirror,dm_log,dm_snapshot
usbhid 34176  0 
hid40928  1 usbhid
ide_cd_mod 30192  0 

Bug#465461: linux-image-2.6.24-1-686: modprobe sbs fails with Unknown parameter `update_time'

[Libor Klepáč]

Hi,
sorry I don't have this notebook anymore. Maybe it was hw problem, several 
components were failing. But under windows, battery status was updating


With regards
Libor

On Wednesday 17 December 2008 22:24:26 Moritz Muehlenhoff wrote:
 On Tue, Feb 12, 2008 at 04:46:22PM +0100, Libor Klepac wrote:
  Package: linux-image-2.6.24-1-686
  Version: 2.6.24-4
  Severity: normal
 
  Hello,
  since upgrading from 2.6.23-2 to 2.6.24-3 and 2.6.24-4, module sbs
  (smart battery system) doesn't load with message
  sbs: Unknown parameter `update_time'
 
  My notebook (acer travelmate 4501WLMi) provides battery status only with
  this module, so without it, it doesn't react on low battery status (it
  died yesterday with flat battery)

 Does this error still occur with more recent kernel versions?

 Cheers,
 Moritz




signature.asc
Description: This is a digitally signed message part.

Bug#495342: libqt4-core: KDE4 system tray with no icons

[Libor Klepáč]

Package: libqt4-core
Version: 4.4.1-1
Severity: normal
Tags: experimental

Hi,
I have installed KDE4.1 on my new laptop, already with qt 4.4.1-1, when i
log in, my system tray is wide, as it has severals icons, but there are
no icons.
Yesterday, I have upgraded my desktop computer(running KDE4.1) from qt4 version 
4.4.0-4
also to 4.4.1-1 and system tray seems to behave in the same way (when i
downgrade back to 4.4.0-4, systray is OK)
Both computers run experimental, both computers use nvidia-glx drivers
from experimental (desktop has gt7600 card and laptop has gt8600go card), both 
computers are arch amd64

With regards

Libor

-- System Information:
Debian Release: lenny/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.25-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libqt4-core depends on:
ii  libqt4-dbus   4.4.1-1Qt 4 D-Bus module
ii  libqt4-network4.4.1-1Qt 4 network module
ii  libqt4-script 4.4.1-1Qt 4 script module
ii  libqt4-test   4.4.1-1Qt 4 test module
ii  libqt4-xml4.4.1-1Qt 4 XML module
ii  libqtcore44.4.1-1Qt 4 core module

libqt4-core recommends no packages.

libqt4-core suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#492462: please split openttd to openttd and openttd-data

[Libor Klepáč]

Package: openttd
Version: 0.6.2~rc1-1
Severity: wishlist

Hello,
have you considered spliting openttd to binary and data package
(architecture all)?
Binary package is 1MB big and data package is 1.7MB big. I think, that after
openttd gets new(32bpp) graphics, data package will get even bigger and it will
save space when there will be just one data package.
I have attached modified debian/ dir (oneline change in rules and
renaming of control files).

With regards

Libor

-- System Information:
Debian Release: lenny/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openttd depends on:
ii  debconf [debconf-2.0]  1.5.23Debian configuration management sy
ii  libc6  2.7-12GNU C Library: Shared libraries
ii  libfontconfig1 2.6.0-1   generic font configuration library
ii  libfreetype6   2.3.7-1   FreeType 2 font engine, shared lib
ii  libgcc11:4.3.1-7 GCC support library
ii  libpng12-0 1.2.27-1  PNG library - runtime
ii  libsdl1.2debian1.2.13-2  Simple DirectMedia Layer
ii  libstdc++6 4.3.1-7   The GNU Standard C++ Library v3
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

openttd recommends no packages.

Versions of packages openttd suggests:
pn  freepats  none (no description available)
pn  timidity  none (no description available)

-- debconf information:
* openttd/datafiles:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.0
Source: openttd
Binary: openttd, openttd-data
Architecture: any
Version: 0.6.2~rc1-1.1
Maintainer: Matthijs Kooijman [EMAIL PROTECTED]
Uploaders: Jordi Mallach [EMAIL PROTECTED]
Homepage: http://www.openttd.org/
Standards-Version: 3.7.3
Vcs-Browser: http://svn.debian.org/wsvn/collab-maint/deb-maint/openttd/trunk/
Vcs-Svn: svn://svn.debian.org/svn/collab-maint/deb-maint/openttd/trunk
Build-Depends: debhelper (= 4.0.0), dpatch, libsdl-dev, zlib1g-dev, 
libpng-dev, libfreetype6-dev, libfontconfig-dev
Checksums-Sha1: 
 650d4155f6217a962046b71910b1e8ba836f0f8b 4943453 openttd_0.6.2~rc1.orig.tar.gz
 c2342b0b7e129254cd504720157c0b5a7669f971 9040 openttd_0.6.2~rc1-1.1.diff.gz
Checksums-Sha256: 
 3287879f3b1a2e5839a721025cd34851ec4db065f28a5b903f580296009bbc1c 4943453 
openttd_0.6.2~rc1.orig.tar.gz
 e9c6ba04ced5dd1c9ae668143c33d33aa7cedd31214f69f5f41b16dea0a86498 9040 
openttd_0.6.2~rc1-1.1.diff.gz
Files: 
 bc1f95da0aacc324a77ad32c5f016379 4943453 openttd_0.6.2~rc1.orig.tar.gz
 42d4108a926d320324b8fa2d801030af 9040 openttd_0.6.2~rc1-1.1.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkiK3zoACgkQhMrxGRe1HmHupgCeNTSbpzukievsjG2pzw1O26hX
9agAn2L2MNloVfBTdRShrwFS/lRVgeKM
=YRRo
-END PGP SIGNATURE-


openttd_0.6.2~rc1-1.1.diff.gz
Description: GNU Zip compressed data

Bug#465461: linux-image-2.6.24-1-686: SBS still broken

[Libor Klepáč]

Package: linux-image-2.6.24-1-686
Version: 2.6.24-6
Followup-For: Bug #465461

Hello,
I'm writing about the problem, with which I started this bug report (so
no Dell machine here ;) )

I found out, that lockups are really caused by my graphics card, fglrx
or xserver-xorg-video-ati beyond version 1:6.7.197-1 causes computer to
lockup (with fglrx - just launch glxinfo-lockup)

But i still have problem with sbs module - battery levels are not
updated as battery charges/discharges, which is very unpleasant. I also
tried kernel 2.6.25 and another battery but results are the same.
I think, problem are the unkown lines

cat /proc/acpi/battery/BAT0/info
present: yes
design capacity: 4400 mAh
last full capacity:  2065 mAh
battery technology:  rechargeable
design voltage:  14800 mV
design capacity warning: unknown
design capacity low: unknown
capacity granularity 1:  unknown
capacity granularity 2:  unknown
model number:01ZL
serial number:   6243
battery type:LION
OEM info:SANYO

cat /proc/acpi/battery/BAT0/info
present: yes
design capacity: 4400 mAh
last full capacity:  1690 mAh
battery technology:  rechargeable
design voltage:  14400 mV
design capacity warning: unknown
design capacity low: unknown
capacity granularity 1:  unknown
capacity granularity 2:  unknown
model number:02ZL
serial number:   15179
battery type:Lion
OEM info:Panasonic


CU

Libor


-- Package-specific info:
** Kernel log:
intel_rng: FWH not detected
parport_pc 00:08: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7, dma 3 
[PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
sbshc: no version for struct_module found: kernel tainted.
ACPI: SBS HC: EC = 0xf7c79b00, offset = 0x18, query_bit = 0x20
ACPI: PCI Interrupt :00:1f.3[B] - Link [LNKB] - GSI 10 (level, low) - 
IRQ 10
input: Video Bus as /class/input/input5
ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED]
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt :02:04.0[A] - Link [LNKB] - GSI 10 (level, low) - 
IRQ 10
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
Synaptics Touchpad, model: 1, fw: 5.9, id: 0x126eb1, caps: 0xa04713/0x4000
input: SynPS/2 Synaptics TouchPad as /class/input/input6
ACPI: Smart Battery System [SBS0]: AC Adapter [AC0] (on-line)
nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 1.
nsc-ircc, chip-init
nsc-ircc, Found chip at base=0x164e
nsc-ircc, driver loaded (Dag Brattli)
ACPI: Smart Battery System [SBS0]: Battery Slot [BAT0] (battery present)
ipw2200: Radio Frequency Kill Switch is On:
Kill switch must be turned off for wireless networking to work.
ipw2200: Detected geography ZZM (11 802.11bg channels, 0 802.11a channels)
IrDA: Registered device irda0
nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500
ACPI: PCI Interrupt :02:06.3[A] - Link [LNKE] - GSI 10 (level, low) - 
IRQ 10
Yenta: CardBus bridge found at :02:06.0 [1025:0064]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket :02:06.0, mfunc 0x01a21b22, devctl 0x64
ACPI: Smart Battery System [SBS0]: Battery Slot [BAT1] (battery absent)
Yenta: ISA IRQ mask 0x0830, PCI irq 10
Socket status: 3006
Yenta: Raising subordinate bus# of parent bus (#02) from #02 to #06
pcmcia: parent PCI bridge I/O window: 0x4000 - 0x4fff
cs: IO port probe 0x4000-0x4fff: clean.
pcmcia: parent PCI bridge Memory window: 0xd020 - 0xd05f
udev: renamed network interface eth1 to eth2
ACPI: PCI Interrupt :00:1f.6[B] - Link [LNKB] - GSI 10 (level, low) - 
IRQ 10
PCI: Setting latency timer of device :00:1f.6 to 64
cs: IO port probe 0x100-0x3af: clean.
cs: IO port probe 0x3e0-0x4ff: clean.
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xc00-0xcf7: clean.
cs: IO port probe 0xa00-0xaff: clean.
MC'97 0 converters and GPIO not ready (0x1)
ACPI: PCI Interrupt :00:1f.5[B] - Link [LNKB] - GSI 10 (level, low) - 
IRQ 10
PCI: Setting latency timer of device :00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 55914 usecs
intel8x0: clocking to 48000
Adding 682720k swap on /dev/hda5.  Priority:-1 extents:1 across:682720k
loop: module loaded
fuse init (API version 7.9)
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 1.5.6_OSE (interface 0x00050002).
RPC: Registered udp transport module.
RPC: 

Bug#465461: linux-image-2.6.24-1-686: modprobe sbs fails with Unknown parameter `update_time'

[Libor Klepáč]

Hi,
i'm sorry, it was my fault, i have this line

options sbs update_time=10

in /etc/modprobe.d/local

After comenting it out, module loads, but my notebook freezes hard, doesn't 
respond to magic sysrq even.
2.6.24 boot freezes on HAL starting up, 2.6.23 boots most times, but sometimes 
freezes after KDE is started.
I suppose, this is hw problem, because i was using 2.6.24 for few days and 
2.6.23 for weeks.

CU
Libor


signature.asc
Description: This is a digitally signed message part.

Bug#443518: ldm: Debian theme is ugly

[Libor Klepáč]

Hello,
i think, it's ok - at least after you make background of debian logo 
transparent instead of white

libor


signature.asc
Description: This is a digitally signed message part.

Bug#439768: libmtp5: udev rules prevents using my player in mass storage mode

[Libor Klepáč]

Hello,
today, there was upgrade of amarok which was rebuild against libmtp6.
It seems it works nicely now.
Thanks

Libor

Dne út 28. srpna 2007 jste napsal(a):
 package libmtp5
 tags 439768 moreinfo
 thanks

 * Libor Klepac [EMAIL PROTECTED] [2007-08-27 11:43]:
  Package: libmtp5
  Version: 0.1.5-2
  Severity: important
 
  hello,
  when i put my sansa e250 in mass storage mode, it's still somehow
  influenced by rules in libmtp.rules - block devices are not created.
  I managed to solve? this problem by adding line
  DRIVER==usb-storage, GOTO=libmtp_rules_end
  just bellow
  SUBSYSTEM!=usb_device, ACTION!=add, GOTO=libmtp_rules_end
 
  It works fine for me now, but i don't know, if that is the right
  approach

 Could you please try libmtp6 and see if the problem persists?




signature.asc
Description: This is a digitally signed message part.

Bug#439768: libmtp5: udev rules prevents using my player in mass storage mode

[Libor Klepáč]

Dne út 28. srpna 2007 jste napsal(a):
 package libmtp5
 tags 439768 moreinfo
 thanks

 * Libor Klepac [EMAIL PROTECTED] [2007-08-27 11:43]:
  Package: libmtp5
  Version: 0.1.5-2
  Severity: important
 
  hello,
  when i put my sansa e250 in mass storage mode, it's still somehow
  influenced by rules in libmtp.rules - block devices are not created.
  I managed to solve? this problem by adding line
  DRIVER==usb-storage, GOTO=libmtp_rules_end
  just bellow
  SUBSYSTEM!=usb_device, ACTION!=add, GOTO=libmtp_rules_end
 
  It works fine for me now, but i don't know, if that is the right
  approach

 Could you please try libmtp6 and see if the problem persists?

hello,
i don't use mtp mode, but amarok package depends on libmtp5, so it's installed 
in my system

libor

(sorry about double report into bts, i found it now, is there some way to 
remove second mail from bts?)


signature.asc
Description: This is a digitally signed message part.

Bug#439771: libmtp5: udev rules prevents using my player in mass storage mode

[Libor Klepáč]

Package: libmtp5
Version: 0.1.5-2
Severity: important

hello,
when i put my sansa e250 in mass storage mode, it's still somehow
influenced by rules in libmtp.rules - block devices are not created.
I managed to solve? this problem by adding line
DRIVER==usb-storage, GOTO=libmtp_rules_end
just bellow
SUBSYSTEM!=usb_device, ACTION!=add, GOTO=libmtp_rules_end

It works fine for me now, but i don't know, if that is the right
approach

cu

libor


-- System Information:
Debian Release: lenny/sid
  APT prefers experimental
  APT policy: (700, 'experimental'), (700, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.23-rc2-l2-1 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libmtp5 depends on:
ii  libc6 2.6.1-1GNU C Library: Shared libraries
ii  libusb-0.1-4  2:0.1.12-7 userspace USB programming library
ii  udev  0.114-2/dev/ and hotplug management 
daemo

libmtp5 recommends no packages.

-- no debconf information


signature.asc
Description: This is a digitally signed message part.

Bug#383891: closed by [EMAIL PROTECTED] (martin f. krafft) (Bug#383891: fixed in mdadm 2.5.3.git200608202239-1)

[Libor Klepáč]

hello,
i still have problem booting with 
root=UUID=23b82182-17bf-4751-b74c-3d9b51a78fe9 + initramfs (today, i was 
rebooting for the first time since the bug was closed)
there is no link in /dev/disk/by-uuid, after rootdelay timeouts, when i run 
udevtrigger it apears and system continues booting 
i tried to place udevtrigger into mdadm script in local-top.
I also tried to copy part of mdadm script, which modprobes modules to 
init-premount and made udev depend on it.

Both methods did not work, i'll try the second method but i'll make mdadm 
depend on udev and i'll report what happens.


cu libor


pgpiXPetkfX2C.pgp
Description: PGP signature

Bug#383891: mdadm: fix for 381181 prevents udev creating /dev/disk/* links

[Libor Klepáč]

hello,
just a small modification, to take /dev/md/* and /dev/md* into account

--
for dev in `grep ^md /proc/mdstat | sed -r 's/^md([0-9]+).*/\1/'`; do
if [ -b /dev/md/$dev ]; then
dev=/dev/md/$dev
elif [ -b /dev/md$dev ]; then
dev=/dev/md$dev
else
continue
fi
if [ `/lib/udev/vol_id -l $dev` !=  ]; then
ln -fs $dev /dev/disk/by-label/`/lib/udev/vol_id -l $dev`
fi
if [ `/lib/udev/vol_id -u $dev` !=  ]; then
ln -fs $dev /dev/disk/by-uuid/`/lib/udev/vol_id -u $dev`
fi
done
--

cu
libor


pgpKFUktY2nQD.pgp
Description: PGP signature

Bug#335202: apt-cacher: does not support pdiffs

[Libor Klepáč]

hello, 
i believe, it can be fixed with this little patch.

cu

libor klepac
--- apt-cacher.orig	2005-12-11 01:06:22.0 +0100
+++ apt-cacher	2005-12-11 01:06:43.0 +0100
@@ -67,6 +67,8 @@
 	'Sources.gz',
 	'Sources.bz2',
 	'Contents-.+\.gz',
+	'[0-9]{4}-[0-9]{2}-[0-9]{2}-[0-9]{4}.[0-9]{2}.gz',
+	'Index',
 );
 my $index_files_regexp = '(' . join('|', @index_files) . ')$';
 


pgp8Qah0H9EPS.pgp
Description: PGP signature

Bug#342002: nagios: per service obsess over service cgi iface patch

[Libor Klepáč]

hello,
i forgot to attach diff of common.h

libor klepac
--- orig/common/common.h	2004-10-25 04:32:20.0 +0200
+++ new/common/common.h	2005-12-04 18:32:30.0 +0100
@@ -156,6 +156,8 @@
 #define CMD_SCHEDULE_HOSTGROUP_SVC_DOWNTIME 85 /* not internally implemented */
 #define CMD_SCHEDULE_HOST_SVC_DOWNTIME  86
 
+#define CMD_ENABLE_SVC_OBSESS_OVER_SERVICE		200
+#define CMD_DISABLE_SVC_OBSESS_OVER_SERVICE		201
 
 
 / SERVICE CHECK TYPES /


pgpcTMOQZkimZ.pgp
Description: PGP signature

Bug#342002: nagios: per service obsess over service cgi iface patch

[Libor Klepáč]

and diff on extinfo.css ... kill me now, people ;)
--- orig/html/stylesheets/extinfo.css	2002-05-11 02:44:12.0 +0200
+++ new/html/stylesheets/extinfo.css	2005-12-04 22:18:39.0 +0100
@@ -61,6 +61,9 @@
 	.flapdetectionENABLED { font-family: arial,serif; font-size: 10pt; text-align: left; background-color: #33FF00; font-weight: bold; }
 	.flapdetectionDISABLED { font-family: arial,serif; font-size: 10pt; text-align: left; background-color: #F83838; font-weight: bold; }
 
+	.obsessoverserviceENABLED { font-family: arial,serif; font-size: 10pt; text-align: left; background-color: #33FF00; font-weight: bold; }
+	.obsessoverserviceDISABLED { font-family: arial,serif; font-size: 10pt; text-align: left; background-color: #F83838; font-weight: bold; }
+
 	.notflapping { font-family: arial,serif; font-size: 10pt; text-align: left; background-color: #33FF00; font-weight: bold; }
 	.flapping { font-family: arial,serif; font-size: 10pt; text-align: left; background-color: #F83838; font-weight: bold; }
 


pgpsgLgYaOqrY.pgp
Description: PGP signature

Bug#339966: webalizer: crashes on (compatible; Googlebo t-Mobile/2.1; +http://www.google.com/bot.html) agent

[Libor Klepáč]

Package: webalizer
Version: 2.01.10-27

hello,
i have noticed, that webalizer crashes, when parsing some of our numerous 
apache logs.
I have been little investigating and isolated this line in logs
66.249.72.204 - - [18/Nov/2005:19:40:08 +0100] GET / HTTP/1.1 200 4781 - 
Nokia6820/2.0 (4.83) Profile/MIDP-1.0 Configuration/CLDC-1.0 (compatible; 
Googlebot-Mobile/2.1; +http://www.google.com/bot.html)

After trying to find out whats wrong, i found out, that replacing ';' 
character following Googlebot-Mobile/2.1 does the trick. 
When you remove it still segfaults , when you add another ; somewhere segfault 
stays.
I can get rid of it, when i set MangleAgents to 2 (we use 1)

i run it thru debugger, i think, it crashes on line 843 in webalizer.c
while (*cp1!=')'*cp1!='\0') *cp2++=*cp1++;

but it looks like some king of magic :)

can you please tell me whats wrong?

thanks

libor klepac


pgpRhtZyAvgbB.pgp
Description: PGP signature