Bug#979332: Anyone working on this ? Is it just need some packaging work?

[Andrew Worsley]

Hi I would like to see some progress on this as I use dokuwiki. I am
willing to help out but I don't know what
the resolution would look like.

Is it just a matter of re-packaging something more modern in a way
that avoids a particular issue?

I am certainly no PHP expert so it would be a fair amount of learning
for me to work on that if that is required?

Andrew

Bug#966476: git-svn: dcommit doesn't preserve author field when authors file used

[Andrew Worsley]

Package: git-svn
Version: 1:2.20.1-2+deb10u3
Severity: important
Tags: patch



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1), 
LANGUAGE=en_GB:en_AU:en (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages git-svn depends on:
ii  git   1:2.20.1-2+deb10u3
ii  libsvn-perl   1.10.4-1+deb10u1
ii  libterm-readkey-perl  2.38-1
ii  libyaml-perl  1.27-1

git-svn recommends no packages.

Versions of packages git-svn suggests:
pn  git-doc 
ii  subversion  1.10.4-1+deb10u1

-- no debconf information

  As described in stack overflow issue in 2011 and verified in this version
  as still present:


https://stackoverflow.com/questions/5327924/git-svn-dcommit-with-svn-usernames

  I find that the commit (at least for file URL subversion) just uses the 
default
  which is the last username used to submit changes to subversion.

  It is fairly easy to make up a simple subversion project to demonstrate the
  problem.

mkdir proj
touch proj/README.txt
svn import proj file://$(pwd)/repo -m "Initial checkin"
SVN_URL=file://$(pwd)/repo
svn co $SVN_URL proj.svn
echo "Change from fred" >> proj.svn/README.txt
svn commit --username fred proj.svn/README.txt -m "Change #1 from fred"
cat > authors.txt
amw = Andrew Worsley 
fred = Fred Smith 
^D

 # Export to git via git-svn
git svn clone --authors-file=authors.txt $SVN_URL proj.git-svn
 # The log shows the authors file is working svn => git
git -C proj.git-svn log

  # Add a change from user fred shows it appears as fred as
  # this was the last user to submit change into subversion:
echo "Change #2 from fred" >> proj.git-svn/README.txt
git -C proj.git-svn commit README.txt --author='Fred Smith 
' -m "2nd change from user fred"
git -C proj.git-svn log
commit 6c203a7022cd831fe505918967bda0534106cd09 (HEAD -> master)
Author: Fred Smith 
Date:   Wed Jul 29 10:52:36 2020 +1000

2nd change from user fred

commit 16b1728f0fe30a9c42098ad42b8da37a7b4405da (git-svn)
Author: Fred Smith 
Date:   Wed Jul 29 00:43:58 2020 +

Change #1 from fred

git-svn-id: file:///build/tmp/repo@2 bb13463d-1302-4b91-af5e-7ea19058a0f6

commit 2e2138b9af3bc8445f5fcba8e2e4c77e3ea78349
Author: Andrew Worsley 
Date:   Wed Jul 29 00:40:09 2020 +

Initial checkin

git-svn-id: file:///build/tmp/repo@1 bb13463d-1302-4b91-af5e-7ea19058a0f6

  # Now try it as user amw (which is my login user)
echo "Change #2 from amw" >> proj.git-svn/README.txt
git -C proj.git-svn commit README.txt -m "2nd change from user amw"
git -C proj.git-svn log
commit 5704bbe7bc60a3a6f29ca4122706fdc648cde2e1 (HEAD -> master)
Author: Andrew Worsley 
Date:   Wed Jul 29 10:54:48 2020 +1000

2nd change from user amw

commit 5398dbf30ee59d579bc7b2a60bab5f4088254cdf (git-svn)
Author: Fred Smith 
Date:   Wed Jul 29 00:53:20 2020 +

2nd change from user fred

git-svn-id: file:///build/tmp/repo@3 bb13463d-1302-4b91-af5e-7ea19058a0f6

commit 16b1728f0fe30a9c42098ad42b8da37a7b4405da
Author: Fred Smith 
Date:   Wed Jul 29 00:43:58 2020 +

Change #1 from fred

git-svn-id: file:///build/tmp/repo@2 bb13463d-1302-4b91-af5e-7ea19058a0f6

commit 2e2138b9af3bc8445f5fcba8e2e4c77e3ea78349
Author: Andrew Worsley 
Date:   Wed Jul 29 00:40:09 2020 +

Initial checkin

git-svn-id: file:///build/tmp/repo@1 bb13463d-1302-4b91-af5e-7ea19058a0f6

  # Now we dcommit this 2nd amw change
git -C proj.git-svn svn dcommit
Committing to file:///build/tmp/repo ...
M   README.txt
Committed r4
M   README.txt
r4 = bb626e195128d9582447a10d664f04323ae8c2b9 (refs/remotes/git-svn)
No changes between 5704bbe7bc60a3a6f29ca4122706fdc648cde2e1 and 
refs/remotes/git-svn
Resetting to the latest refs/remotes/git-svn

   # But it was commited into subversion as being from user fred !
 svn log -v $SVN_URL

r4 | fred | 2020-07-29 10:55:05 +1000 (Wed, 29 Jul 2020) | 1 line
Changed paths:
   M /README.txt

2nd change from user amw

r3 | fred | 2020-07-29 10:53:20 +1000 (Wed, 29 Jul 2020) | 1 line
Changed paths:
   M /README.txt

2nd change from user fred

r2 | fred | 2020-07-29 10:43:58 +1000 (Wed, 29 Jul 2020) | 1 line
Changed paths:
   M /README.txt

Change #1 from fred

r1 | amw | 20

Bug#882640: Closing the ITP for dm-zoned-tools as I have uploaded a package

[Andrew Worsley]

Thanks very one for your help - sorry for making a hash of it.
I guess I wait for the mail to debian-mentors mailing to be sorted and perhaps
by the end of this week - try sending it again.


On Tue, 19 Mar 2019 at 15:51, Paul Wise  wrote:
>
> On Sat, 2019-03-16 at 17:08 +1100, Andrew Worsley wrote:
>
> > Closing the ITP for dm-zoned-tools as I have uploaded a package
>
> The ITP should only be closed when the package reaches Debian. Normally
> this happens automatically when a package with (Closes: #123456) in the
> Debian changelog file reaches the archive. Bart Martens has corrected
> this premature closing by reopening the bug.

  Ok - my changelog does have the Closes: #882640 line - but I assumed that
uploading it to mentors area counted - but I guess it needs a sponsor first.
So I'll be patient and wait

> > I opened another RFS bug 924708:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924708
> >
> > I think I slightly mucked up the RFP as I used the reportbug and
> > pasted in a description into the wrong field - but it seems to be ok.
>
> Bart Martens corrected the title of the RFS bug report to be more like
> the RFS template. In addition the newcomer tag is not meant to be used
> in the way that you used it because the idea of the tag is to indicate
> bugs that aren't being worked on right now but that a new contributor
> could work on, Andrey Rahmatullin corrected that by removing the tag.

 Thanks again Andrey and Bart. I didn't notice this work until you
pointed it out to me.

> https://mentors.debian.net/sponsors/rfs-howto
> https://www.debian.org/Bugs/Developer#tags
>
> Somehow your RFS bug report didn't reach the debian-mentors mailing
> list. I have resent the mail to the list but the mail still didn't
> reach the list so I think there must be some sort of filtering.
> I have asked the #debian-lists channel what happened there.

  Ok - Still haven't seen any progress on this - perhaps I should just
manually post it?

...
>
> > I believe I have fixed all the issues that I know how to do - it
> > claims the watch file doesn't work - but it seems to work for me?
>
> I expect this is because the mentors site uses an old version of
> devcripts but your watch file uses the new git support. In addition,
> phpmode is not a valid option in watch files, I think you meant the
> pgpmode option.
>

Thanks for explaining why this isn't working.
  I have removed the phpmode option - I think it was cruft left over
from dh_make example.
Not sure it's worth re-doing for just this item so I'll wait to see if
there are any more fixes.

Thanks

Andrew

Bug#920482: apt update fails to update from repository missing optional Contents files

[Andrew Worsley]

On Sat, 26 Jan 2019, 6:57 pm Julian Andres Klode  On Sat, Jan 26, 2019 at 12:39:16PM +1100, Andrew Worsley wrote:
> > Package: apt
> > Version: 1.8.0~alpha3.1
> > Severity: important
> >
> >
> >   I maintain a mirror via a local python script which doesn't bother to
> cache the optional
> > Contents files as described in
> > https://wiki.debian.org/DebianRepository/Format#A.22Contents.22_indices
> :
> >
> 
>


> I think that's correct. While the Contents files are optional; if the
> Release file advertises
> them, they better be there.
>
> Partial mirroring is simply not supported - if you advertise it, ship it.
> I mean, the same
> applies to architectures or sections: If they're not mirrored, but enabled
> on a client,
> they will fail as well
>
...
Ok thanks that's clarified things a lot.
I guess if I don't want to mirror the contents file I would have to edit
the InRelease file which would break the signatures I guess.
 The option that marks the contents as missing also lets me handle this
nicely.
Ideally this could be added to the repository definition wiki and or
perhaps apt's error message could say file defined in InRelease file is not
present.
 Perhaps change but report into a wish list or something?
Andrew

>

Bug#920482: apt update fails to update from repository missing optional Contents files

[Andrew Worsley]

Now fixed by purging the apt-file package!
Big thanks to pabs on IRC #debian-apt for this solution.

Note: You need to purge the package to make sure the config file
apt-file supplies is removed to fix this problem (remove is *NOT*
enough)

Apparently apt-file no works by using apt-get to install the Contents
target for that file.
This can be configure as described in
/usr/share/doc/apt-file/README.md.gz for certain repositories via a
line like:
[target-=Contents-deb] $MIRROR/debian unstable main ...

Bug#920482: apt update fails to update from repository missing optional Contents files

[Andrew Worsley]

Package: apt
Version: 1.8.0~alpha3.1
Severity: important


  I maintain a mirror via a local python script which doesn't bother to cache 
the optional
Contents files as described in
https://wiki.debian.org/DebianRepository/Format#A.22Contents.22_indices :

"They are optional indices describing which files can be found in which 
packages"

  But whilst my debian stretch box happily upgrades my stretch mirror my buster
mirror is no longer wanting to upgrade my testing box.

  If I add a URL for my mirror and an official mirror ftp.au.debian.org and do 
an update
it appears to fail to update from my mirror complaining about the missing 
Contents file:

% sudo apt update
[sudo] password for amw:
Get:1 http://azza/debs/buster buster InRelease [159 kB]
Get:2 http://azza/debs/buster buster/main amd64 Packages [10.6 MB]
Get:3 http://azza/debs/buster buster/main Translation-en [5,966 kB]
Get:4 http://azza/debs/buster buster/main amd64 Contents (deb) [36.5 MB]
Get:4 http://azza/debs/buster buster/main amd64 Contents (deb) [36.5 MB]
Get:4 http://azza/debs/buster buster/main amd64 Contents (deb) [36.5 MB]
Get:4 http://azza/debs/buster buster/main amd64 Contents (deb) [36.5 MB]
Ign:4 http://azza/debs/buster buster/main amd64 Contents (deb)
Ign:9 http://azza/debs/buster buster/contrib amd64 Contents (deb)
Ign:10 http://azza/debs/buster buster/non-free amd64 Contents (deb)
Err:4 http://azza/debs/buster buster/main amd64 Contents (deb)
  404  Not Found [IP: 10.0.0.51 80]
Ign:9 http://azza/debs/buster buster/contrib amd64 Contents (deb)
Ign:10 http://azza/debs/buster buster/non-free amd64 Contents (deb)
Hit:11 http://ftp.au.debian.org/debian buster InRelease
Fetched 159 kB in 2s (67.0 kB/s)
Reading package lists... Done
E: Failed to fetch http://azza/debs/buster/dists/buster/main/Contents-amd64  
404  Not Found [IP: 10.0.0.51 80]
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

   Even though my mirror has that up to date version of the packages and the 
InRelease
   and Packages.gz files are up to date and list the new version of packages 
won't
   install it from my mirror.

% apt-cache policy vim
vim:
  Installed: 2:8.1.0549-1
  Candidate: 2:8.1.0693-2
  Version table:
 2:8.1.0693-2 500
500 http://ftp.au.debian.org/debian buster/main amd64 Packages
 *** 2:8.1.0549-1 100
100 /var/lib/dpkg/status

   It appears the Error on the Contents file prevents the azza repository 
Package data
   from being loaded?

   This appears to be a recent problem - i.e. the last couple of weeks.

   I have not changed my mirror script to start mirroring Contents file to 
confirm
   this is the key difference. If Content files are meant to be mandatory now 
could
   the Wiki page be updated?

   I tried asking on the #debian-apt IRC but got no answer so raising a 
bugreport

Thanks

Andrew

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.19\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.18\.0-3-amd64$";
APT::NeverAutoRemove:: 

Bug#855349: Your mail

[Andrew Worsley]

On Sat, 1 Jul 2017 20:55:01 +0200 pre...@terta.de wrote:
> for me an
>
>
> $ apt-get remove kscreensaver kscreensaver-xsavers
>
> and
>
> $ apt autoremove
>
> solved the issue.
>

Nothing worked for me while I had the stretch repositories in my
/etc/apt/sources.list.
Once I went back to strictly jessie entries and did an update then I
could finally remove the
problematic kde packages and *then* add back in the stretch entries
and finally update

I ended up removing

dolphin kdepimlibs-kio-plugins thunderbird

and then did the
apt-get autoremove

Then added back in the stretch (but not stretch/updates) repository entry

Then got:
...
Selecting previously unselected package udev.
dpkg: regarding .../udev_232-25+deb9u2_amd64.deb containing udev:
 udev conflicts with hal
  hal (version 0.5.14-8) is present and installed.

dpkg: error processing archive
/var/cache/apt/archives/udev_232-25+deb9u2_amd64.deb (--unpack):
 conflicting packages - not installing udev
dpkg: considering deconfiguration of ifupdown, which would be broken
by installation of systemd ...
dpkg: yes, will deconfigure ifupdown (broken by systemd)
Preparing to unpack .../systemd_232-25+deb9u2_amd64.deb ...
De-configuring ifupdown (0.7.53.1) ...
Unpacking systemd (232-25+deb9u2) over (215-17+deb8u8) ...
Preparing to unpack .../ifupdown_0.8.19_amd64.deb ...
Unpacking ifupdown (0.8.19) over (0.7.53.1) ...
Preparing to unpack .../liblvm2app2.2_2.02.168-2_amd64.deb ...
Unpacking liblvm2app2.2:amd64 (2.02.168-2) over (2.02.111-2.2+deb8u1) ...
Preparing to unpack .../lvm2_2.02.168-2_amd64.deb ...
Unpacking lvm2 (2.02.168-2) over (2.02.111-2.2+deb8u1) ...
Preparing to unpack .../libdevmapper1.02.1_2%3a1.02.137-2_amd64.deb ...
Unpacking libdevmapper1.02.1:amd64 (2:1.02.137-2) over
(2:1.02.90-2.2+deb8u1) ...
Preparing to unpack .../dmsetup_2%3a1.02.137-2_amd64.deb ...
Unpacking dmsetup (2:1.02.137-2) over (2:1.02.90-2.2+deb8u1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Errors were encountered while processing:
 /var/cache/apt/archives/udev_232-25+deb9u2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Then did the suggested

apt-get install -f
 
175 upgraded, 68 newly installed, 52 to remove and 2146 not upgraded.
305 not fully installed or removed.
Need to get 0 B/97.9 MB of archives.
After this operation, 177 MB disk space will be freed.
Do you want to continue? [Y/n]
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
setting xserver-xorg-legacy/xwrapper/allowed_users from configuration file
(Reading database ... 403552 files and directories currently installed.)
Removing jackd2-firewire (1.9.10+20150825git1ed50c92~dfsg-5) ...
(Reading database ... 403547 files and directories currently installed.)
Preparing to unpack .../klibc-utils_2.0.4-9_amd64.deb ...
Adding 'diversion of /usr/share/initramfs-tools/hooks/klibc to
/usr/share/initramfs-tools/ho


Then I got
...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-3.16.0-7-amd64
W: initramfs-tools configuration sets
RESUME=UUID=09d39f7b-2f6e-4cfc-86fe-97da40d7b784
W: but no matching swap device is available.
I: The initramfs will attempt to resume from /dev/sdd3
I: (UUID=8ace5863-41ee-4d43-8dc3-d0b2aa9bf7ef)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.36.5-2+deb9u2) ...
Processing triggers for dbus (1.10.26-0+deb9u1) ...
Processing triggers for menu (2.1.47) ...
Errors were encountered while processing:
 rpcbind
 nfs-common
 nfs-kernel-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

   An apt-get install -f
failed intermediately again

and apt-get autoremove also gives similar errors

Setting up rpcbind (0.2.3-0.6) ...
A dependency job for rpcbind.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript rpcbind, action "start" failed.
● rpcbind.service - RPC bind portmap service
   Loaded: loaded (/lib/systemd/system/rpcbind.service; enabled;
vendor preset: enabled)
   Active: active (exited) since Tue 2002-01-01 11:03:19 AEDT; 17
years 0 months ago
 Docs: man:rpcbind(8)
   CGroup: /system.slice/portmap.service

Jan 18 13:14:58 azza systemd[1]: rpcbind.service changed dead -> running
Jan 18 13:20:12 azza systemd[1]: rpcbind.service changed dead -> running
Jan 18 13:20:26 azza systemd[18724]: Executing: /etc/init.d/rpcbind stop
Jan 18 13:20:31 azza systemd[1]: rpcbind.service changed dead -> exited
Jan 18 17:54:03 azza systemd[1]: Dependency failed for RPC bind portmap service.
Jan 18 17:54:03 azza systemd[1]: rpcbind.service: Job
rpcbind.service/start failed wit…ncy'.
Jan 18 17:57:31 azza systemd[1]: Dependency failed for RPC bind portmap service.
Jan 18 17:57:31 azza systemd[1]: rpcbind.service: Job
rpcbind.service/start failed wit…ncy'.
Jan 18 17:58:08 azza systemd[1]: 

Bug#882640: Fwd: dm-zoned-tools uploaded to mentors.debian.net

[Andrew Worsley]

Deleted the previous upload and uploaded the package again to get a
clean the upload and fix the revision numbers.
The original revision number implied it was built from upstream
release 1.0.1 which was not correct.

Fixed the various issues mentioned in previous package comments.

-- Forwarded message -
From: mentors.debian.net 
Date: Fri, 4 Jan 2019 at 18:41
Subject: dm-zoned-tools uploaded to mentors.debian.net
To: 


Hi.

Your upload of the package 'dm-zoned-tools' to mentors.debian.net was
successful. Others can now see it. The URL of your package is:
https://mentors.debian.net/package/dm-zoned-tools

The respective dsc file can be found at:
https://mentors.debian.net/debian/pool/main/d/dm-zoned-tools/dm-zoned-tools_0.0~git20180830.9188cc0-1.dsc

If you do not yet have a sponsor for your package you may want to go to
https://mentors.debian.net/sponsors/rfs-howto/dm-zoned-tools
and set the "Seeking a sponsor" option to highlight your package on the
welcome page.

You can also send an RFS (request for sponsorship) to the debian-mentors
mailing list. Your package page will give your suggestions on how to
send that mail.

Good luck in finding a sponsor!

Thanks,

--
mentors.debian.net

Bug#882640: Fwd: dm-zoned-tools uploaded to mentors.debian.net

[Andrew Worsley]

Please sponsor the dm-zoned-tools package if you want the dmzadm tool
packaged for debian


-- Forwarded message -
From: mentors.debian.net 
Date: Wed, 19 Dec 2018 at 22:09
Subject: dm-zoned-tools uploaded to mentors.debian.net
To: 


Hi.

Your upload of the package 'dm-zoned-tools' to mentors.debian.net was
successful. Others can now see it. The URL of your package is:
https://mentors.debian.net/package/dm-zoned-tools

The respective dsc file can be found at:
https://mentors.debian.net/debian/pool/main/d/dm-zoned-tools/dm-zoned-tools_1.0.1-5.dsc

If you do not yet have a sponsor for your package you may want to go to
https://mentors.debian.net/sponsors/rfs-howto/dm-zoned-tools
and set the "Seeking a sponsor" option to highlight your package on the
welcome page.

You can also send an RFS (request for sponsorship) to the debian-mentors
mailing list. Your package page will give your suggestions on how to
send that mail.

Good luck in finding a sponsor!

Thanks,

--
mentors.debian.net

Bug#882640: Uploaded dm-zoned-tools package

[Andrew Worsley]

I saw your talk where you asked for a packaging of the dmzadm tool.

I am not a debian developer but am aiming to try and become one.
Anyway I created a debian package (using deb_make) and built it and
uploaded it to my debian mentor account

https://mentors.debian.net/packages/uploader/amworsley%40gmail.com

So if you are still interested please check out the package and sponsor it.

It hasn't turned up yet - it should be called dm-zoned-tools_1.0.1-6
(The .5 was missing the original source package) and I didn't upload
earlier ones.

This was the output from dput - showing it uploading.

Andrew

dput  mentors dm-zoned-tools_1.0.1-6_amd64.changes

Checking signature on .changes
gpg: /home/amw/src/dm-zoned-tools_1.0.1-6_amd64.changes: Valid
signature from D96454E2B3CB734E
Checking signature on .dsc
gpg: /home/amw/src/dm-zoned-tools_1.0.1-6.dsc: Valid signature from
D96454E2B3CB734E
Uploading to mentors (via ftp to mentors.debian.net):
  Uploading dm-zoned-tools_1.0.1-6.dsc: done.
  Uploading dm-zoned-tools_1.0.1.orig.tar.xz: done.
  Uploading dm-zoned-tools_1.0.1-6.debian.tar.xz: done.
  Uploading dm-zoned-tools-dbgsym_1.0.1-6_amd64.deb: done.
  Uploading dm-zoned-tools_1.0.1-6_amd64.buildinfo: done.
  Uploading dm-zoned-tools_1.0.1-6_amd64.deb: done.
  Uploading dm-zoned-tools_1.0.1-6_amd64.changes: done.
Successfully uploaded packages.

Bug#867667: I can confirm this bug is still present in debian stretch 0.999-5

[Andrew Worsley]

The work around as described in the Ubuntu version works ok for me.

https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/1410756

Opening the preview page with the Ctrl-1 and then shutting down and
restarting it starts with the preview pane with all the buttons
displayed
and working properly. - Thank God for this work around - really
annoying otherwise.

Andrew

Bug#409048: ITP celtx

[Andrew Worsley]

I am not sure if I should start off a new bug for this - but here goes.

I have found a version on github which I branched to here
https://github.com/amworsley/celtx

I have managed to compile it under stetch into a binary that starts up
- but doesn't do very much at the moment. I think it is not
able to find it's examples and other structural issues.

I could do with some guidance on where to go further .

It appears to bear a lot of resemblance to mozilla browser so anyone
who understands that build system would be useful or
has used the system in the past so I can try loading up an example.

Thanks

Andrew

Bug#844788: 4.16-rc3 fails to resume on MacBookPro10,1 -

[Andrew Worsley]

On 11 March 2018 at 21:34, Pavel Machek  wrote:
> Hi!
>

>>
>> Ok - all the test modes work but a full s2ram hangs (never comes back)
>> and obviously the resume full save to disk fails.
>>
>> I attach the following files:
>>
>> echo reboot > /sys/power/disk
>> echo disk > /sys/power/state
>> Then saved dmesg to file  dmesg-reboot-disk-ok.txt
>
> So with "reboot" mode, hibernation works as expected, you just have to
> power down machine manually?

 Sorry no all the test modes immediately start back with the
restore faultlessly.
There is no time to power off the machine once it is suspended.
 The hibernate command from the other modes fails as before.
I tried running the hibernate command with shutdown and reboot setting
in /sys/power/disk and the power turns off by itself after 10 or so
seconds in all those modes and the subsequent boot up will resume up
to the hang in the usual place:
 do_idle() / cpu_start_entry()/start_secondary()/
secondary_startup_64()   state.


>
>> I tried to add some debug to hibernation_restore() but saw nothing.
>>  Not sure if I doing this correctly but I believe the last know dmesg
>> entry is from swsusp_read() in kernel/power/swap.c
>> but then I should see something in hibernation_restore() but as the
>> console might not work or something I can't be sure
>>
>> Further directions appreciated
>
> You may want to try without thunderbolt support / talk to thunderbolt
> people:
>
> pciehp seems to have bad problems, too.
>
> I'd suggest debugging with s2ram (as it is less tricky) and removing
> all modules you don't really need.
>
> Good luck,
> Pavel


  ThanksI tried removing the thunderbolt module - the pciehp doesn't
seem to be loaded or is called something else.
The thunderbolt module sometimes complains loudly when remove but made
no difference.

Thanks for your suggestions I will try the s2ram but it seems to be
stuck badly - no interrupts or messages - black screen so it doesn't
seem so easy to make progress. I am more tempted to add printk()s to
the hibernate but I feat there is a tricky point where it calls
routines to suspend console 

Funny it hibernates and resumes so well in the 3.16 kernel...

Andrew

Bug#844788: 4.16-rc3 fails to resume on MacBookPro10,1 -

[Andrew Worsley]

On 3 March 2018 at 16:41, Andrew Worsley <amwors...@gmail.com> wrote:
> Basically hangs on resuming after decompressing. The last statement
> displayed is "resume: Image successfully loaded"
>  - I attach a photo as I can't get access to it

> Bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844788
>
> I couldn't get anything from the function keys with this latest kernel.
...

By plugging in a USB keyboard I can get sysrq stuff to work - but
stupidly the kernel disables all the useful ones so I will have to
compile a new kernel with it set to 1 so I can get some traces.
Really annoyed by this default setting, presumably from debian?
Wished there was a boot command line option to configure the allowed options.

Andrew

Bug#888722: More details - AVCs from systemd journal + audit2allow output

[Andrew Worsley]

audit2allow output:

#= semanage_t ==
allow semanage_t debugfs_t:dir write;
allow semanage_t device_t:dir write;
allow semanage_t hugetlbfs_t:dir write;
allow semanage_t root_t:dir write;
allow semanage_t security_t:dir write;
allow semanage_t semanage_tmp_t:file execute;
allow semanage_t sysctl_fs_t:dir search;
allow semanage_t tmpfs_t:dir { search write };
allow semanage_t user_home_dir_t:dir write;
allow semanage_t user_runtime_t:dir write;


  * Also tried to see if my filesystem needed some re-labelling

root@kvm:/home/amw# restorecon -R -F -v -n / |& wc
   1886   13121  281001

* I tried a relable


touch  /.autorelabel ; reboot

But there are still 352  entries and the semanage login -l still fails...

* So I did the restorecon and that eliminates everything except warnings
...
Warning no default label for /sys/kernel/debug/ras
...

 * But the semanage login -l still fails exactly the same.

 * So I started building the policy based on the output of audit2allow
and the following fixed things:

policy_module(local-semanage, 1.2)

require {
   type semanage_t, semanage_tmp_t, root_t;
   type device_t, security_t;
}
allow semanage_t root_t:dir write;
allow semanage_t security_t:dir write;
allow semanage_t device_t:dir write;
allow semanage_t semanage_tmp_t:file execute;

root@kvm:~/pol-semanage# semanage login -l

Login Name   SELinux User MLS/MCS RangeService

__default__  unconfined_u s0-s0:c0.c1023   *
root unconfined_u s0-s0:c0.c1023   *
system_u system_u s0-s0:c0.c1023   *

* Actually by trial and error I confirmed that the single following
file was necessary and sufficient to fix the problem!

policy_module(local-semanage, 1.3)

require {
   type semanage_t, semanage_tmp_t, root_t;
   type device_t, security_t;
}
#allow semanage_t root_t:dir write;
#allow semanage_t security_t:dir write;
#allow semanage_t device_t:dir write;
allow semanage_t semanage_tmp_t:file execute;
[ 1821.256883] kvm audit[826]: AVC avc:  denied  { execute } for  pid=826 
comm="semanage" path=2F746D702F233130323631202864656C6574656429 dev="vda1" 
ino=10261 scontext=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 
tcontext=unconfined_u:object_r:semanage_tmp_t:s0 tclass=file permissive=0
[ 1821.257200] kvm audit[826]: SYSCALL arch=c03e syscall=9 success=no 
exit=-13 a0=0 a1=1000 a2=5 a3=1 items=0 ppid=732 pid=826 auid=1000 uid=0 gid=0 
euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=1 comm="semanage" 
exe="/usr/bin/python3.5" 
subj=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 key=(null)
[ 1821.257314] kvm audit: PROCTITLE 
proctitle=2F7573722F62696E2F707974686F6E33002D4573002F7573722F7362696E2F73656D616E616765006C6F67696E002D6C
[ 1821.257490] kvm audit[826]: AVC avc:  denied  { execute } for  pid=826 
comm="semanage" path=2F7661722F746D702F233130323631202864656C6574656429 
dev="vda1" ino=10261 
scontext=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 
tcontext=unconfined_u:object_r:semanage_tmp_t:s0 tclass=file permissive=0
[ 1821.257617] kvm audit[826]: SYSCALL arch=c03e syscall=9 success=no 
exit=-13 a0=0 a1=1000 a2=5 a3=1 items=0 ppid=732 pid=826 auid=1000 uid=0 gid=0 
euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=1 comm="semanage" 
exe="/usr/bin/python3.5" 
subj=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 key=(null)
[ 1821.257717] kvm audit: PROCTITLE 
proctitle=2F7573722F62696E2F707974686F6E33002D4573002F7573722F7362696E2F73656D616E616765006C6F67696E002D6C
[ 1821.257883] kvm audit[826]: AVC avc:  denied  { write search } for  pid=826 
comm="semanage" name="/" dev="tmpfs" ino=8713 
scontext=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 
tcontext=system_u:object_r:tmpfs_t:s0 tclass=dir permissive=0
[ 1821.257982] kvm audit[826]: SYSCALL arch=c03e syscall=2 success=no 
exit=-13 a0=7fe25669ab37 a1=490082 a2=1c0 a3=1 items=0 ppid=732 pid=826 
auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 
ses=1 comm="semanage" exe="/usr/bin/python3.5" 
subj=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 key=(null)
[ 1821.258075] kvm audit: PROCTITLE 
proctitle=2F7573722F62696E2F707974686F6E33002D4573002F7573722F7362696E2F73656D616E616765006C6F67696E002D6C
[ 1821.258210] kvm audit[826]: AVC avc:  denied  { write } for  pid=826 
comm="semanage" name="root" dev="vda1" ino=7867 
scontext=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 
tcontext=system_u:object_r:user_home_dir_t:s0 tclass=dir permissive=0
[ 1821.258308] kvm audit[826]: SYSCALL arch=c03e syscall=2 success=no 
exit=-13 a0=7fffa04a1ecb a1=490082 a2=1c0 a3=1 items=0 ppid=732 pid=826 
auid=1000 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 
ses=1 comm="semanage" exe="/usr/bin/python3.5" 
subj=unconfined_u:unconfined_r:semanage_t:s0-s0:c0.c1023 key=(null)
[ 1821.258448] kvm audit: PROCTITLE 

Bug#888722: [DSE-Dev] Bug#888722: policycoreutils-python-utils: semanage port -a fails when python3-numpy is installed

[Andrew Worsley]

I get a very similar failure doing a simple " semanage login -l "

root@kvm:/home/amw# semanage login -l
Traceback (most recent call last):
  File "/usr/sbin/semanage", line 28, in 
import seobject
  File "/usr/lib/python3/dist-packages/seobject.py", line 34, in 
import sepolicy
  File "/usr/lib/python3/dist-packages/sepolicy/__init__.py", line 8,
in 
import setools
  File "/usr/lib/python3/dist-packages/setools/__init__.py", line 74,
in 
from .infoflow import InfoFlowAnalysis
  File "/usr/lib/python3/dist-packages/setools/infoflow.py", line 22,
in 
import networkx as nx
  File "/usr/lib/python3/dist-packages/networkx/__init__.py", line 93,
in 
import networkx.linalg
  File "/usr/lib/python3/dist-packages/networkx/linalg/__init__.py",
line 9, in 
from networkx.linalg.algebraicconnectivity import *
  File 
"/usr/lib/python3/dist-packages/networkx/linalg/algebraicconnectivity.py",
line 18, in 
from numpy import (array, asmatrix, asarray, dot, matrix, ndarray, ones,
  File "/usr/lib/python3/dist-packages/numpy/__init__.py", line 142, in 
from . import add_newdocs
  File "/usr/lib/python3/dist-packages/numpy/add_newdocs.py", line 13,
in 
from numpy.lib import add_newdoc
  File "/usr/lib/python3/dist-packages/numpy/lib/__init__.py", line 8,
in 
from .type_check import *
  File "/usr/lib/python3/dist-packages/numpy/lib/type_check.py", line
11, in 
import numpy.core.numeric as _nx
  File "/usr/lib/python3/dist-packages/numpy/core/__init__.py", line
33, in 
from . import _internal  # for freeze programs
  File "/usr/lib/python3/dist-packages/numpy/core/_internal.py", line
14, in 
import ctypes
  File "/usr/lib/python3.5/ctypes/__init__.py", line 537, in 
_reset_cache()
  File "/usr/lib/python3.5/ctypes/__init__.py", line 276, in _reset_cache
CFUNCTYPE(c_int)(lambda: None)
MemoryError

  * I repeated it with an strace got suspect this snippet might be relevant:


stat("/usr/lib/python3.5", {st_mode=S_IFDIR|0755, st_size=12288, ...}) = 0
stat("/usr/lib/python3.5/ctypes/__init__.cpython-35m-x86_64-linux-gnu.so",
0x7ffc31b69430) = -1 ENOENT (No such file or directory)
stat("/usr/lib/python3.5/ctypes/__init__.abi3.so", 0x7ffc31b69430) =
-1 ENOENT (No such file or directory)
stat("/usr/lib/python3.5/ctypes/__init__.so", 0x7ffc31b69430) = -1
ENOENT (No such file or directory)
stat("/usr/lib/python3.5/ctypes/__init__.py", {st_mode=S_IFREG|0644,
st_size=16847, ...}) = 0
stat("/usr/lib/python3.5/ctypes/__init__.py", {st_mode=S_IFREG|0644,
st_size=16847, ...}) = 0
open("/usr/lib/python3.5/ctypes/__pycache__/__init__.cpython-35.pyc",
O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=17508, ...}) = 0
lseek(3, 0, SEEK_CUR)   = 0
fstat(3, {st_mode=S_IFREG|0644, st_size=17508, ...}) = 0
read(3, 
"\27\r\r\n\370\310\200X\317A\0\0\343\0\0\0\0\0\0\0\0\0\0\0\0\f\0\0\0@\0\0"...,
17509) = 17508
read(3, "", 1)  = 0
close(3)= 0
mmap(NULL, 262144, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x7f56e00a8000
open("/tmp", O_RDWR|O_EXCL|O_DIRECTORY|O_CLOEXEC|O_TMPFILE, 0700) = 3
ftruncate(3, 4096)  = 0
mmap(NULL, 4096, PROT_READ|PROT_EXEC, MAP_SHARED, 3, 0) = -1 EACCES
(Permission denied)
close(3)= 0
open("/var/tmp", O_RDWR|O_EXCL|O_DIRECTORY|O_CLOEXEC|O_TMPFILE, 0700) = 3
ftruncate(3, 4096)  = 0
mmap(NULL, 4096, PROT_READ|PROT_EXEC, MAP_SHARED, 3, 0) = -1 EACCES
(Permission denied)
close(3)= 0
open("/dev/shm", O_RDWR|O_EXCL|O_DIRECTORY|O_CLOEXEC|O_TMPFILE, 0700)
= -1 EACCES (Permission denied)
open("/root", O_RDWR|O_EXCL|O_DIRECTORY|O_CLOEXEC|O_TMPFILE, 0700) =
-1 EACCES (Permission denied)
open("/etc/mtab", O_RDONLY|O_CLOEXEC)   = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "sysfs /sys sysfs rw,seclabel,nos"..., 1024) = 1024
access("/dev", W_OK)= -1 EACCES (Permission denied)
access("/", W_OK)   = -1 EACCES (Permission denied)
access("/sys/fs/selinux", W_OK) = -1 EACCES (Permission denied)
access("/dev/shm", W_OK)= -1 EACCES (Permission denied)
read(3, "oup rw,nosuid,nodev,noexec,relat"..., 1024) = 1024
access("/proc/sys/fs/binfmt_misc", W_OK) = -1 EACCES (Permission denied)
access("/sys/kernel/debug", W_OK)   = -1 EACCES (Permission denied)
access("/dev/mqueue", W_OK) = -1 EACCES (Permission denied)
access("/dev/hugepages", W_OK)  = -1 EACCES (Permission denied)
read(3, "/1000 tmpfs rw,seclabel,nosuid,n"..., 1024) = 90
access("/run/user/1000", W_OK)  = -1 EACCES (Permission denied)
read(3, "", 1024)   = 0
close(3)= 0
open("/proc/mounts", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(3, "sysfs /sys sysfs rw,seclabel,nos"..., 1024) = 1024
access("/dev", W_OK)   

Bug#844788: Still failing hibernate/resume with stretch backport kernel linux-image-4.14.0-0.bpo.3-amd64

[Andrew Worsley]

Again on resume it just says "resume: Image successfully loaded" and
then nothing much See previous  image attached.
 I do get an additional interrupt related message when I plug in and
then remove my USB ethernet device.
So it seems the system is running but the display is not working.

I can reboot the laptop by ctrl-alt-del key combination which
apparently causes it to reboot.

Andrew

Bug#877296: Subject: RFS: dokuwiki-sync/0.1 ITP

[Andrew Worsley]

Package: sponsorship-requests
Severity: wishlist
Dear mentors,

This is just a small shell script I have used from time to time - I am
not sure how usable it is for others and it is mostly to get practise
of packaging and getting feedback. So please feel free to comment on
what might be a better tool or way to handle the task of synchronising
two wiki'd (dokuwiki based in this case only).

  I am looking for a sponsor for my package "dokuwiki-sync"

 * Package name: dokuwiki-sync
   Version : 0.1
   Upstream Author : Andrew Worsley <amwors...@gmail.com>
 * URL :  https://github.com/amworsley/dokuwiki-sync
 * License : GPL 2.0
   Section : admin

  It builds those binary packages:

dokuwiki-sync - synchronise dokuwiki trees

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/dokuwiki-sync


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/d/dokuwiki-sync/dokuwiki-sync_0.1.dsc

  More information about hello can be obtained from https://www.example.com.

  Initial Release to get any comments

  Regards,
   Andrew Worsley

Bug#844788: suspending from VGA makes no difference - stuck at the same place.

[Andrew Worsley]

Also just wanted to add that running all kernels with command lines:
nomodeset nointremap acpi=none vga=0x34c


Also all the modes in /sys/power/pm_test (except none) are fine in the
problematic 4.7.0 kernel - even with "nomodeset nointremap acpi=none"
kernel options removed.

Still hangs on resuming in 4.7.0

In the 3.16.7-ckt25 kernel is the only one that is fine for resume...
(except it also wants these "nomodeset nointremap acpi=none" boot
options otherwise I get kernel complaints...

dmidecode:1012 freeing invalid memtype [me
m 0x3fff8ad1b000-0x3fff8ad1bfff]
Nov 23 21:01:14 localhost kernel: [   10.122979] dmidecode: Corrupted
page table at address
7f10d9da7000
Nov 23 21:01:14 localhost kernel: [   10.122982] PGD 45c7c7067 PUD
45c774067 PMD 45d95f067
PTE 8ad1b225
Nov 23 21:01:14 localhost kernel: [   10.122985] Bad pagetable: 000d [#3] SMP

Bug#844788: Just also tried the latest unstable and the latest experimental with the same results.

[Andrew Worsley]

linux-image-4.8.0-1-amd64-unsigned_4.8.7-1_amd64
.deb

and

linux-image-4.9.0-rc5-amd64-unsigned_4.9~rc5-1~e
xp1_amd64.deb

Bug#844788: hibernate: suspends ok but hangs on restore after decompressing with stretch kernel on macbook pro

[Andrew Worsley]

Just tested out the latest testing linux-image-amd64:amd64 4.8+76 with
exactly the same results.

Perhaps this is a kernel bug?

Bug#844788: hibernate: suspends ok but hangs on restore after decompressing with stretch kernel on macbook pro

[Andrew Worsley]

Package: hibernate
Version: 2.0+15+g88d54a8-1
Severity: important


  I have an older jessie kernel linux-image-3.16.7-ckt25 (with quirk
  patches for disabling the wireless which macbook bios leaves enabled)
  and that works very well. I can suspend and resume many times.

  But the current debian stretch kernel will suspend fine but hangs on restore 
*just* as it
  has finished expending the image into memory. It looks like it has
  worked but is just stuck on the restoring screen at 100% but not
  responsive to any keys.

  From dmesg:

 DMI: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS 
MBP101.88Z.00EE.B0A.1509111559 09/11/2015

 Happy to re-compile kernels/switch on additional debugging, run other
 commands or re-log to another package if that is more appropriate.

 Kind of not sure where to go other than digging into the code myself -
 which I don't know where to start at...


 Andrew



-- Package-specific info:
--- configuration
==> /etc/hibernate/common.conf <==
Verbosity 4
LogFile /var/log/hibernate.log
LogVerbosity 4
Distribution debian
SaveClock restore-only
OnSuspend 20 echo "Good night!"
OnResume 20 echo "Good morning!"
UnloadBlacklistedModules yes
LoadModules auto
DownInterfaces wlan3
SwitchToTextMode yes
==> /etc/hibernate/disk.conf <==
TryMethod ususpend-disk.conf
TryMethod sysfs-disk.conf
==> /etc/hibernate/hibernate.conf <==
TryMethod tuxonice.conf
TryMethod disk.conf
TryMethod ram.conf
==> /etc/hibernate/ram.conf <==
TryMethod ususpend-ram.conf
TryMethod sysfs-ram.conf
==> /etc/hibernate/sysfs-disk.conf <==
UseSysfsPowerState disk
Include common.conf
==> /etc/hibernate/sysfs-ram.conf <==
UseSysfsPowerState mem
Include common.conf
==> /etc/hibernate/tuxonice.conf <==
UseTuxOnIce yes
Reboot no
EnableEscape yes
DefaultConsoleLevel 1
Compressor lzo
Encryptor none
FullSpeedCPU yes
Include common.conf
==> /etc/hibernate/ususpend-both.conf <==
USuspendMethod both
Include common.conf
==> /etc/hibernate/ususpend-disk.conf <==
USuspendMethod disk
Include common.conf
==> /etc/hibernate/ususpend-ram.conf <==
USuspendMethod ram
Include common.conf

--- /sys/power
==> /sys/power/disk <==
[platform] shutdown reboot suspend 
==> /sys/power/image_size <==
9714061926
==> /sys/power/pm_async <==
1
==> /sys/power/pm_freeze_timeout <==
2
==> /sys/power/pm_print_times <==
0
==> /sys/power/pm_test <==
[none] core processors platform devices freezer
==> /sys/power/reserved_size <==
1048576
==> /sys/power/resume <==
8:6
==> /sys/power/state <==
freeze mem disk
==> /sys/power/wakeup_count <==
3

--- s2ram -n
Machine unknown
This machine can be identified by:
sys_vendor   = ""
sys_product  = ""
sys_version  = ""
bios_version = ""
--- log
Starting suspend at Thursday 17 November 23:44:59 AEDT 2016
hibernate: [01] Executing CheckLastResume ... 
hibernate: [01] Executing CheckRunlevel ... 
hibernate: [01] Executing LockFileGet ... 
hibernate: [01] Executing NewKernelFileCheck ... 
hibernate: [10] Executing EnsureUSuspendCapable ... 
hibernate: [11] Executing XHacksSuspendHook1 ... 
hibernate: [20] Executing MiscLaunchAuxFunc1 ... 
Executing echo "Good night!"...
Good night!
hibernate: [59] Executing RemountXFSBootRO ... 
hibernate: [60] Executing NetworkStop ... 
hibernate: [89] Executing SaveKernelModprobe ... 
hibernate: [91] Executing ModulesUnloadBlacklist ... 
hibernate: [95] Executing XHacksSuspendHook2 ... 
hibernate: [98] Executing CheckRunlevel ... 
hibernate: [99] Executing DoUSuspend ... 
hibernate: Running /usr/sbin/s2disk ...
hibernate: [90] Executing ModulesLoad ... 
hibernate: [89] Executing RestoreKernelModprobe ... 
hibernate: [85] Executing XHacksResumeHook2 ... 
hibernate: [70] Executing ClockRestore ... 
hibernate: [60] Executing NetworkStart ... 
hibernate: [59] Executing RemountXFSBootRW ... 
hibernate: [20] Executing MiscLaunchAuxFunc2 ... 
Executing echo "Good morning!"...
Good morning!
hibernate: [11] Executing XHacksResumeHook1 ... 
hibernate: [01] Executing NoteLastResume ... 
hibernate: [01] Executing LockFilePut ... 
Resumed at Saturday 19 November 14:09:13 AEDT 2016

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 3.16.7-ckt25-b43-earlyquirk-freset (SMP w/8 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages hibernate depends on:
ii  dpkg  1.18.10
ii  kbd   2.0.3-2

Versions of packages hibernate recommends:
ii  dash 0.5.8-2.3
ii  hdparm   9.48+ds-2
ii  uswsusp  1.0+20120915-6.1
ii  vbetool  1.1-4

Versions of packages hibernate suggests:
pn  915resolution
pn  xscreensaver | kscreensaver | gnome-screensaver | xlock | vlock  

-- Configuration Files:
/etc/hibernate/blacklisted-modules changed:
acx100
acx_pci
hsfmodem
prism54
bcm4400 2.6.0   3.99.0

Bug#844058: dokuwiki: Upgraded from jessie and apache2 module PHP was not enabled so pages were not rendered.

[Andrew Worsley]

Package: dokuwiki
Version: 0.0.20160626.a-1
Severity: important


  I was able to get it to start working by merely enabling the PHP-7.0
  module via:
 sudo a2enmod 

 and typing 

  php7.0

  It then asked me to run 

 systemctl restart apache2

  which I did. Now it is working fine

 Thanks

Andrew

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel

Kernel: Linux 3.16.7-ckt25-b43-earlyquirk-freset (SMP w/8 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dokuwiki depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  javascript-common  11
ii  libjs-jquery   3.1.1-1
ii  libjs-jquery-cookie11-3
ii  libjs-jquery-ui1.12.1+dfsg-1
ii  libphp-simplepie   1.3.1+dfsg-3.1
ii  php1:7.0+45
ii  php-geshi  1.0.8.11-2.1
ii  php-seclib 1.0.5-1
ii  php-xml1:7.0+45
ii  php7.0 [php]   7.0.12-1
ii  php7.0-xml [php-xml]   7.0.12-1
ii  ucf3.0036

Versions of packages dokuwiki recommends:
ii  imagemagick  8:6.9.6.2+dfsg-2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.6.2+dfsg-2
ii  php-ldap 1:7.0+45
ii  php7.0-cli [php-cli] 7.0.12-1
ii  php7.0-ldap [php-ldap]   7.0.12-1
ii  wget 1.18-4

Versions of packages dokuwiki suggests:
pn  libapache2-mod-xsendfile  

-- Configuration Files:
/etc/dokuwiki/dokuwiki.php changed [not included]

-- debconf information:
  dokuwiki/wiki/policy: public
* dokuwiki/system/accessible: localhost only
* dokuwiki/system/writeplugins: true
* dokuwiki/wiki/license: cc-by-sa
* dokuwiki/system/writeconf: true
* dokuwiki/system/configure-webserver: apache2
  dokuwiki/wiki/failpass:
* dokuwiki/wiki/title: MacBook DokuWiki
  dokuwiki/wiki/email: webmaster@localhost
* dokuwiki/system/documentroot: /dokuwiki
  dokuwiki/wiki/superuser: admin
* dokuwiki/system/purgepages: false
* dokuwiki/system/restart-webserver: true
* dokuwiki/wiki/acl: true
  dokuwiki/wiki/fullname: DokuWiki Administrator
  dokuwiki/system/localnet: 10.0.0.0/24

Bug#822671: initramfs-tools: preserves unmodified /etc/initramfs-tools/initramfs.conf on upgrades from jessie

[Andrew Worsley]

On 2 October 2016 at 07:15, Ben Hutchings <b...@decadent.org.uk> wrote:
> On Fri, 2016-09-30 at 09:57 +1000, Andrew Worsley wrote:
>> Hi, I am a newbie (have a mentor account and looking to help)
>> I just looked into this bug and tried to apply the patch - but it
>> appears the files are missing - perhaps way out of date?
> [...]
>
> The patch applies for me with 'patch -p1'.  But I haven't yet taken the
> time to try it out.
>
> Ben.

  Sorry I got confused and was apply to an older (0.120 version) it applies
 perfectly for me against 0.125 the latest version. I believe version
looks ok to
a basic piuparts but I am having troubles testing a distribution
upgrade with piuparts
but that might be a  limitation of piuparts or my knowledge on how to run it.

Help on how to proceed would be appreciated.

It may well be that the unpatched version is fine now - I did most of
my testing with the patched
package.

* I checked it with a basic piuparts :
  piuparts initramfs-tools_0.125_all.deb

  * and got a complaint:

4m20.9s ERROR: FAIL: Package purging left files on system:
  /var/log/apt/eipp.log.xz   not owned


  I got this on the unpatched *and* the patched version of the package.
It turns out this is a piupart bug - fixed in version 0.72
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830527

I upgraded to backports version of piuparts:
  apt-get install piuparts/jessie-backports

vagrant(0)% piuparts --version
piuparts 0.72~bpo8+1

and it is much happier:
  * piuparts -s piuparts-base.tgz initramfs-tools-core_0.125+nmu1_all.deb

4m55.5s DEBUG: Removed directory tree at /tmp/tmpJyGQJ8
4m55.5s INFO: PASS: All tests.
4m55.5s INFO: piuparts run ends.

  * Running the .changes file into a log and grep-ing the info entries
all looks good.
   piuparts -b piuparts-base.tgz -l piuparts-log.txt
initramfs-tools_0.125+nmu1_amd64.changes

0m24.5s INFO: Installation of
['tmp/initramfs-tools-core_0.125+nmu1_all.deb',
'tmp/initramfs-tools_0.125+nmu1_all.deb'] ok
0m25.8s INFO: Running adequate version 0.12.1 now.
0m27.7s INFO: PASS: Installation, upgrade and purging tests.
0m28.0s INFO: PASS: All tests.
0m28.0s INFO: piuparts run ends.

  * Trying to run an upgrade test fails:
piuparts -b piuparts-base.tgz -l piuparts-log2.txt -d jessie -d
stretch initramfs-tools_0.125+nmu1_amd64.changes

1m12.5s DEBUG: Starting command: ['chroot', '/tmp/tmpcZJKsf',
'eatmydata', 'apt-get', '-y', 'install', 'initramfs-tools']
1m12.8s DUMP:
  Reading package lists...
  Building dependency tree...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   initramfs-tools : Depends: udev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
1m12.8s ERROR: Command failed (status=100): ['chroot',
'/tmp/tmpcZJKsf', 'eatmydata', 'apt-get', '-y', 'install',
'initramfs-tools']
  Reading package lists...
  Building dependency tree...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   initramfs-tools : Depends: udev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.



Is there a way to do this with piuparts or  do I have to figure out
some way to testing this by actually physically upgrading my vagrant
box to stretch and checking if there are files left behind?

Finally if the patched version is worth applying what other functional
tests should be considered to validate the patched version?

Thanks

Andrew

Bug#822671: initramfs-tools: preserves unmodified /etc/initramfs-tools/initramfs.conf on upgrades from jessie

[Andrew Worsley]

Hi, I am a newbie (have a mentor account and looking to help)
I just looked into this bug and tried to apply the patch - but it
appears the files are missing - perhaps way out of date?

Perhaps still has errors as piuparts that I ran reported a problem
with the latest package I built.

If it is welcome I am willing to investigate and try to fix this.

If I am way off track let me know so I don't waste people's time
(including mine :-)

I also just tried to run piuparts in a (vagrant box in case it messed
up my own initramfs ?) and still getting an error:

...
6m17.1s DEBUG: No broken symlinks as far as we can find.
6m17.1s DEBUG: Starting command: ['chroot', '/tmp/tmpJWYJRD',
'eatmydata', 'dpkg-divert', '--list']
6m17.1s DUMP:
  diversion of /usr/share/man/man1/sh.1.gz to
/usr/share/man/man1/sh.distrib.1.gz by dash
  diversion of /bin/sh to /bin/sh.distrib by dash
6m17.1s DEBUG: Command ok: ['chroot', '/tmp/tmpJWYJRD', 'eatmydata',
'dpkg-divert', '--list']
6m17.1s DEBUG: Starting command: ['chroot', '/tmp/tmpJWYJRD',
'eatmydata', 'apt-get', 'clean']
6m17.1s DEBUG: Command ok: ['chroot', '/tmp/tmpJWYJRD', 'eatmydata',
'apt-get', 'clean']
6m17.4s ERROR: FAIL: Package purging left files on system:
  /etc/bash_completion.d/not owned
  /etc/bash_completion.d/initramfs-tools.dpkg-newnot owned
  /var/log/apt/eipp.log.xz   not owned

6m17.4s ERROR: FAIL: Installation and purging test.
...

Andrew Worsley

Bug#837408: RFS: partimage/0.6.9-1 new upstream build partimage-0.6.9

[Andrew Worsley]

Good points - I guess it is not worth making a new package to fix
these items you mention - but the next one I should consider them. See
below for more details


On 11 September 2016 at 23:18, Eriberto Mota  wrote:
> Contol: tag 837408 moreinfo
>
> Hi Andrew,
>
> I have some considerations:
>
> 1. d/changelog:
>
> - You are doing a QA upload. So, it must be in changelog.
>
> - You renamed the patch 03-ftbfs-zlib.patch to 01-ftbfs-zlib. Please,
> point it in changelog.
>
> 2. d/control:
>
> - Please, bump Standards-Version to 3.9.8.
>
> Thanks for your work.
>
> Regards,
>
> Eriberto
>

Thanks for your e-mail I will note the points about the changelog for
next time (as policy says best to fix changelog via an additional
entry).

I didn't check the changes to the Standards-Version field as I didn't
feel expert to look at that so I didn't attempt to update that.

So I have started to trawl through the changes via

/usr/share/doc/debian-policy/upgrading-checklist.txt.gz
 (from stretch which is upto 3.9.8.0)

since partimage-0.6.8 is currently as per Standards-Version 3.9.1.
I  found some things:

3.9.3:
 9.1.1
  `/run' is allowed as an exception to the FHS and replaces
  `/var/run'.  `/run/lock' replaces `/var/lock'.  The FHS
  requirements for the older directories apply to these directories
  as well.  Backward compatibility links will be maintained and
  packages need not switch to referencing `/run' directly yet.
  Files in `/run' should be stored in a temporary file system.
...

 9.1.4
  New section spelling out the requirements for packages that use
  files in `/run', `/var/run', or `/var/lock'.  This generalizes
  information previously only in 9.3.2.

partimage-0.6.9/debian/partimage-server.partimaged.init

has PIDFILE=/var/run/partimaged.pid

The above is ok I guess and otherwise I think the policy is good - so
next build I will bump up the Standards-version level as well.

Thanks  again

Andrew

Bug#640022: closed by Andrew Worsley <amwors...@gmail.com> (Closing this bug as currently builds ok)

[Andrew Worsley]

On 12 September 2016 at 07:41, Dr. Nagy Elemér Kár oly
 wrote:
> Dear Andrew,
>
> To answer your questions:
> We had a home-grown reimaging solution for legacy systems that fit on a 1.44 
> MB floppy disk (containing partimage),
> which we replaced in the five years elapsed since I reported the bug and the 
> workaround.
>
> I think this bug should R.I.P. but stay on-line and searchable ;)
>
> Best wishes,
> Elmar

Hi - thanks for responding - I am guessing you wanted to create a
statically linked binary?

Perhaps re-open with the details you want as a wish list - then
knowing what exactly you are wanting I or someone else could make it
happen?

Andrew

Bug#837408: RFS: partimage/0.6.9-1 new upstream build partimage-0.6.9

[Andrew Worsley]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

  I am looking for a sponsor for my package "partimage"

 * Package name: partimage
   Version : 0.6.9-1
   Upstream Author : Orphaned package
 * URL : http://www.partimage.org/
 * License : GPLv2
   Section : admin

  It builds these binary packages:

partimage  - backup partitions into a compressed image file
 partimage-server - server to use partimage across a network

  To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/partimage


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/partimage/partimage_0.6.9-1.dsc

  More information about hello can be obtained from https://www.example.com.

  Changes since the last upload:
  * New upstream release.
  * Drop now redundant patches as now in new upstream release:
- 01-openssl.patch
- 02-format-security.patch

new upstream release (from upstream's changelog):
0.6.9) 2010-07-25:
applied modifications by Vadim S. (v...@slackware.ru)
applied patch nvieville_server_closenowait_clients_number.patch from
Nicolas Vieville
applied patch nvieville_filesel_NEWT_FLAG_SCROLL.patch from Nicolas Vieville
applied patch partimage-0.6.7-chown.patch from mandriva (on Makefile.am)
applied patch partimage-0.6.8-format-security.patch from mandriva
applied patches from Nicolas Vieville to fix compilation warnings with
gcc-4.4 / glibc-2.10
applied patches from Nicolas Vieville to improve internationalisation
(mostly on partimaged)
applied patches from Nicolas Vieville to free ressources in netclient
(fixes memory leaks)
applied patches from Nicolas Vieville to fix issues with openssl-1.0.0
allow different versions to connect as long as they use the same
protocol and ssl/login options

I have created a vfat image (it still has the same slightly clunky X
windows  / function key interface) and can read the image

  Regards,
   Andrew Worsley

Bug#318135: Perhaps close this bug as not reproducible

[Andrew Worsley]

I have attempted to reproduce this bug on amd64 and ppc and it appears
to work fine.

macbook amw ~ 11:11PM(0)% uname -a
Linux macbook 3.16.7-ckt25-b43-earlyquirk-freset #3 SMP Sat May 28
07:53:49 AEST 2016 x86_64 GNU/Linux
macbook amw ~ 11:08PM(0)% adjtimex -print
 mode: 0
   offset: 0
frequency: 390013
 maxerror: 1600
 esterror: 1600
   status: 64
time_constant: 2
precision: 1
tolerance: 32768000
 tick: 9998
 raw time:  1472908168s 195039us = 1472908168.195039
 return value = 5
macbook amw ~ 11:09PM(0)% sudo adjtimex -print
[sudo] password for amw:
 mode: 0
   offset: 0
frequency: 390013
 maxerror: 1600
 esterror: 1600
   status: 64
time_constant: 2
precision: 1
tolerance: 32768000
 tick: 9998
 raw time:  1472908182s 508062us = 1472908182.508062
 return value = 5
macbook amw ~ 11:09PM(0)% sudo adjtimex -c
  --- current ---   -- suggested --
cmos time system-cmos  error_ppm   tick  freqtick  freq
1472908163  32.284856
1472908173  32.289711  485.5   9998390013
1472908183  32.274508-1520.3   9998390013   10013   1720388
1472908193  32.274974   46.6   99983900139997   3892050
1472908203  32.279633  465.9   99983900139993   2625200
1472908213  32.264351-1528.1   9998390013   10013   2234450
1472908223  32.264783   43.2   99983900139997   4112363
1472908233  32.265210   42.7   99983900139997   4146738


---
On ppc as per original report:

root@imac:/home/amw# uname -a
Linux imac 3.2.0-4-powerpc #1 Debian 3.2.68-1+deb7u6 ppc GNU/Linux

root@imac:/home/amw# adjtimex -c
  --- current ---   -- suggested --
cmos time system-cmos  error_ppm   tick  freqtick  freq
1472907630   0.262813
1472907640   0.2628281.5  1   5590625
1472907650   0.2628542.6  1   5590625   1   5420313
1472907660   0.262992   13.8  1   5590625   1   4687500
1472907670   0.262887  -10.5  1   5590625   1   6278125
1472907680   0.263022   13.5  1   5590625   1   4706250
1472907690   0.262991   -3.1  1   5590625   1   5793750
1472907700   0.263123   13.2  1   5590625   1   4725000
root@imac:/home/amw# adjtimex -print
 mode: 0
   offset: 0
frequency: 5590625
 maxerror: 1600
 esterror: 1600
   status: 64
time_constant: 2
precision: 1
tolerance: 32768000
 tick: 1
 raw time:  1472908193s 539314us = 1472908193.539314
 return value = 5

Bug#775612: Bug is in Perl

[Andrew Worsley]

On Sat, 13 Jun 2015 11:17:02 +0200 (CEST) debian@coelho.net wrote:
..
sh grep StdHash /usr/share/perl/5.20.2/Tie/Hash.pm
# The Tie::StdHash package implements standard perl hash behaviour.
package Tie::StdHash;

 Which means that it seems to be necessary to import Tie::Hash to find
 it, but amanda probably only imports Tie::StdHash.
...
Just thought I should let people know of the work around

I had this problem and found a work around:

 ln -s Hash.pm /usr/share/perl/5.20/Tie/StdHash.pm

This allows the missing or rather hidden definition to be found and doesn't
seem to break anything. i.e. amanda-server package is now working for me nicely.

I used strace on a failing command to see all the file probing/loading
and noticed that
it always loads a .plc ahead of the .pl file. Once I had run the
program with the link it
didn't seem to fail so perhaps the intermittent issue people see is
the compiled perl
versions being found and then later not or being cleaned up?

Andrew

Bug#688971: Here's a very simple patch for adding libcap-dev build dependancy

[Andrew Worsley]

Some one else may have already done this - but here goes anyway.

I have applied it, rebuilt chrony and installed it with a user
configuration entry and verified that it starts up chrony running as
that user
and it is still fetching the time.

sudo adduser --no-create-home --disabled-password  --disabled-login chrony
# Add option: user chrony
sudo vi /etc/chrony/chrony.conf
sudo service chrony stop
sudo service chrony start

# Verified with:
vagrant@debian-jessie:~$ ps -C chronyd -o pid,user,uid,gid
  PID USER   UID   GID
 1375 chrony1001  1001

I will look next at trying to add this as a default option - as
suggested using user ntp - as per ntp package I guess.

Let me know if there is anything else I should do?

Thanks
Andrew
git diff HEAD~ HEAD
diff --git a/chrony-1.30/debian/control b/chrony-1.30/debian/control
index c350027..81df18c 100644
--- a/chrony-1.30/debian/control
+++ b/chrony-1.30/debian/control
@@ -8,7 +8,8 @@ Build-Depends: debhelper (= 9),
  texinfo, bison,
  libedit-dev,
  libnss3-dev,
- libtomcrypt-dev
+ libtomcrypt-dev,
+ libcap-dev
 Homepage: http://chrony.tuxfamily.org
 Vcs-Git: git://anonscm.debian.org/collab-maint/chrony.git
 Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/chrony.git

Bug#688971: Another patch adding support for adding user ntp if not present

[Andrew Worsley]

Also adds configuration to run as user ntp to the configuration file.

I tested it locally in a vagrant debian/jessie virtual machine and it worked.

There are other things that might useful such as updating some documentation.
I may also not have done things exactly right - not being a developer but please
let me know and I can submit another patch.

Andrew
diff --git a/chrony-1.30/debian/changelog b/chrony-1.30/debian/changelog
index 5ecef0f..a188d33 100644
--- a/chrony-1.30/debian/changelog
+++ b/chrony-1.30/debian/changelog
@@ -1,3 +1,10 @@
+chrony (1.30-2amw1) UNRELEASED; urgency=medium
+
+  * Support user configuration option (Closes: #688971)
+   - Causes daemon to drop root priviledges and run as user ntp
+
+ -- Andrew Worsley andrew.worsley a...@tqc.com.au  Sat, 15 Aug 2015 20:58:56 +1000
+
 chrony (1.30-2) unstable; urgency=medium
 
   * With the following security bugfixes (Closes: #782160):
diff --git a/chrony-1.30/debian/chrony.conf b/chrony-1.30/debian/chrony.conf
index e8d9200..6ef0798 100644
--- a/chrony-1.30/debian/chrony.conf
+++ b/chrony-1.30/debian/chrony.conf
@@ -22,6 +22,8 @@ server 1.debian.pool.ntp.org offline minpoll 8
 server 2.debian.pool.ntp.org offline minpoll 8
 server 3.debian.pool.ntp.org offline minpoll 8
 
+# Drop root priviledges and run as ntp
+user ntp
 
 # Look here for the admin password needed for chronyc.  The initial
 # password is generated by a random process at install time.  You may
diff --git a/chrony-1.30/debian/control b/chrony-1.30/debian/control
index 81df18c..c2f2627 100644
--- a/chrony-1.30/debian/control
+++ b/chrony-1.30/debian/control
@@ -21,7 +21,8 @@ Depends: ${misc:Depends},
  ucf, timelimit,
  install-info,
  net-tools,
- lsb-base
+ lsb-base,
+ adduser (= 3.11)
 Recommends: udev (= 0.124-1)
 Conflicts: time-daemon, ntp
 Provides: time-daemon
diff --git a/chrony-1.30/debian/postinst b/chrony-1.30/debian/postinst
index bb13102..119f427 100644
--- a/chrony-1.30/debian/postinst
+++ b/chrony-1.30/debian/postinst
@@ -10,6 +10,14 @@ set -e
 case $1 in
 configure)
 
+if [ -z `id -u ntp 2 /dev/null` ]; then
+echo -n Adding system user ntp
+adduser --system --group --no-create-home --gecos chrony ntp daemon \
+  --no-create-home --disabled-password --quiet ntp || true
+else
+echo -n Using existing user ntp
+fi
+
 cp /usr/share/chrony/chrony.conf /etc/chrony/chrony.conf.new
 MAILUTC=
 TZONE=

Bug#583115: I propose this old bug be closed or more details released

[Andrew Worsley]

I installed the current version chrony:amd64/jessie 1.30-2 uptodate in
a virtual machine and was
not able to fault it's start up.

The script in /etc/init.d/chrony appears to be working fine.

I am using systemd and I am not even sure the script
/etc/init.d/chrony is even used now?

I suggest that no update has happened on this for several years and
there is no sign of the bug
in the current release it be closed.

Otherwise please submit some details . e.g. /etc/chrony/chrony.conf
plus network set up.

Andrew

Bug#776094: dovecot-imapd: corrupts mailbox after trying to retrieve it

[Andrew Worsley]

Sorry it might take me some time to get back to this bug. I was running
Jessie. The key problem here is reproducing the bug. Can you install and
run strace on the dovecot daemon or what ever program you think is messing
up the inbox?

Use -f to follow any fields and -o to save the output to a file. If it
happens so easily for you the should be very easy and would clarify a lot
the exact sequence of events required.

Bug#776094: dovecot-imapd: corrupts mailbox after trying to retrieve it (fwd)

[Andrew Worsley]

On Thu, 19 Feb 2015 22:34:07 +0100 (CET) Santiago Vila sanv...@unex.es wrote:

One more follow up suggestion based on my debugging locally. (You may
already be aware of these options - so forgive me if you already are).

You can install strace and strace the dovecot process e.g.

Run ps axf and look for :

...
 4428 ?Ss 0:00 /usr/sbin/exim4 -bd -q30m
16412 ?Ss 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf
16413 ?S  0:00  \_ dovecot/anvil
16414 ?S  0:00  \_ dovecot/log


Then strace process no 16412 (/usr/sbin/dovecot) via

strace -p16412 -f -s128 -o /tmp/trace

and run your fetchmail command.

This will capture all the system calls into /tmp/trace following forks.

You can examine the open/read/writes it does et cetera. These can be
filtered during the capture with: -e trace=file or -e
trace=open,close,read,write see
what the locking is like.

You can also add -v to fetchmail options for more verbose info.

Finally you can add the following to dovecot.conf configuration file
for extra debug (I think the strace will be more detailed)

debug_log_path = /var/log/dovecot-debug.log
log_path = /var/log/dovecot.log
mail_debug = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u


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

Bug#776094: dovecot-imapd: corrupts mailbox after trying to retrieve it (fwd)

[Andrew Worsley]

On Thu, 19 Feb 2015 22:34:07 +0100 (CET) Santiago Vila sanv...@unex.es wrote:
 On Sun, 15 Feb 2015, Timo Sirainen wrote:

  On 14 Feb 2015, at 16:23, Santiago Vila sanv...@unex.es wrote:
 
   I wrote about this three weeks ago but got no answer. I'm going to
   officially forward the Debian bug this time, with all the details.
  
   The test case is just 840 bytes long. Please give it a try.


I have tried to reproduce this but I don't see a problem.
- but it took me a while to understand what you are trying to do

I ended up with the messages re-appearing into /var/mail/amw which I
then re-copied to the inbox-b and ran fetchmail again.

I did this in a loop and gave up after running it over 250 times with
any corruption.

But note my comment at the bottom I did see one possible configuration
problem on locking files - which isn't set on the default set up - but
it made *NO* difference
to me...

1. I created a vanilla dovecot-imapd installation with one user and
sent some mail to it's account in /var/mail/amw
2. I then created the remote folder by copying the mbox so:
  cp /var/spool/mail/amw /home/amw/mail/inbox-b

3. Then I confirmed the remote folder was ok as below:

  jessie% fetchmail -c localhost --folder  inbox-b
  3 messages for amw at localhost (folder inbox-b).

4. Then I triggered the problem as per:

jessie% fetchmail -a localhost --folder  inbox-b
3 messages for amw at localhost (folder inbox-b).
reading message amw@localhost:1 of 3 (404 header octets) (8 body octets) flushed
reading message amw@localhost:2 of 3 (394 header octets) (10 body
octets) flushed
reading message amw@localhost:3 of 3 (390 header octets) (4 body octets) flushed
jessie% ls -l ~/mail/inbox-b
-rw-r--r-- 1 amw amw 532 Mar 14 16:20 /home/amw/mail/inbox-b
jessie% m ~/mail/inbox-b
From MAILER_DAEMON  Sat Mar 14 16:20:19 2015
Date: Sat, 14 Mar 2015 16:20:19 +1100
From: Mail System Internal Data MAILER-DAEMON@jessie
Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
Message-ID: 1426310419@jessie
X-IMAP: 1426309513 03
Status: RO

This text is part of the internal format of your mail folder, and is not
a real message.  It is created automatically by the mail system software.
If deleted, important folder data will be lost, and it will be re-created
with the data reset to initial values.

  * So this appears to be okay - no corruption .
  * I repeated this in a loop:
while true; do
  cp /var/spool/mail/amw /home/amw/mail/inbox-b  fetchmail -a
localhost --folder  inbox-b -m true  sleep 1 \nT=$(($T+1))
  echo Try $T\nsleep 1
done

Try 253
12 messages for amw at localhost (folder inbox-b).
reading message amw@localhost:1 of 12 (404 header octets) (8 body
octets) flushed
reading message amw@localhost:2 of 12 (394 header octets) (10 body
octets) flushed
reading message amw@localhost:3 of 12 (390 header octets) (4 body
octets) flushed
reading message amw@localhost:4 of 12 (744 header octets) (8 body
octets) flushed
reading message amw@localhost:5 of 12 (733 header octets) (10 body
octets) flushed
reading message amw@localhost:6 of 12 (729 header octets) (4 body
octets) flushed
reading message amw@localhost:7 of 12 (744 header octets) (8 body
octets) flushed
reading message amw@localhost:8 of 12 (733 header octets) (10 body
octets) flushed
reading message amw@localhost:9 of 12 (729 header octets) (4 body
octets) flushed
reading message amw@localhost:10 of 12 (1069 header octets) (10 body
octets) flushed
reading message amw@localhost:11 of 12 (1065 header octets) (4 body
octets) flushed
reading message amw@localhost:12 of 12 (1081 header octets) (8 body
octets) flushed
Try 254
12 messages for amw at localhost (folder inbox-b).
reading message amw@localhost:1 of 12 (404 header octets) (8 body
octets) flushed
reading message amw@localhost:2 of 12 (394 header octets) (10 body
octets) flushed
reading message amw@localhost:3 of 12 (390 header octets) (4 body
octets) flushed
reading message amw@localhost:4 of 12 (744 header octets) (8 body
octets) flushed
...

  * NO problems seen. Am I doing this right?
  * I even tried constantly sending mail to the account but the worse
I got was an occasional error message such as:
...
reading message amw@localhost:104 of 254 (399 header octets) (0 body
octets) flushed
reading message amw@localhost:105 of 254 (399 header octets) (0 body
octets) flushed
fetchmail: Error writing to MDA: Broken pipe
reading message amw@localhost:106 of 254 (399 header octets) (0 body
octets) not flushed
reading message amw@localhost:107 of 254 (399 header octets) (0 body
octets) flushed


but everything kept going...

BUT: the default configuration of /var/mail doesn't have the sticky
bit set nor is the configuration variable *mail_privileged_group* set
to mail - which would
suggest locking might be a problem.

jessie% ls -ld /var/mail
drwxrwsr-x 2 root mail 4096 Mar 14 16:27 /var/mail

Note: I noticed that the dovecot wiki

Bug#752881: Stack Trace

[Andrew Worsley]

After much stuffing around I managed to get a stack trace related to
the change near the problem:


Aug  4 06:20:13 azza kernel: [   12.680555] end_request: I/O error,
dev sr1, sector 0
Aug  4 06:20:13 azza kernel: [   12.685541] sr 6:0:0:0: [sr1]
Unhandled sense code
Aug  4 06:20:13 azza kernel: [   12.686984] sr 6:0:0:0: [sr1]  Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug  4 06:20:13 azza kernel: [   12.688417] sr 6:0:0:0: [sr1]  Sense
Key : Blank Check [current]
Aug  4 06:20:13 azza kernel: [   12.689842] sr 6:0:0:0: [sr1]  Add.
Sense: No additional sense information
Aug  4 06:20:13 azza kernel: [   12.691269] sr 6:0:0:0: [sr1] CDB:
Read(10): 28 00 00 00 00 00 00 00 01 00
Aug  4 06:20:13 azza kernel: [   12.692729] end_request: I/O error,
dev sr1, sector 0
Aug  4 06:20:13 azza kernel: [   13.014699] EXT3-fs (md10): using
internal journal
Aug  4 06:20:13 azza kernel: [   13.140807] dump_bug_752881() -
disk_max_parts(disk)=256, (disk-flags  GENHD_FL_NO_PART_SCAN)=0x200
Aug  4 06:20:13 azza kernel: [   13.142307] Pid: 1123, comm: modprobe
Not tainted 3.2.0-amw-fix3+ #1
Aug  4 06:20:13 azza kernel: [   13.143797] Call Trace:
Aug  4 06:20:13 azza kernel: [   13.145303]  [8119abce] ?
dump_bug_752881+0x4e/0x6a
Aug  4 06:20:13 azza kernel: [   13.146771]  [8119ac85] ?
register_disk+0x9b/0x133
Aug  4 06:20:13 azza kernel: [   13.148239]  [8119995b] ?
blk_register_region+0x22/0x27
Aug  4 06:20:13 azza kernel: [   13.149700]  [8119add2] ?
add_disk+0xb5/0x27f
Aug  4 06:20:13 azza kernel: [   13.151148]  [a03af843] ?
loop_add+0x1c9/0x1f5 [loop]
Aug  4 06:20:13 azza kernel: [   13.152593]  [81039613] ?
should_resched+0x5/0x23
Aug  4 06:20:13 azza kernel: [   13.154028]  [a03b6101] ?
loop_init+0x101/0x1000 [loop]
Aug  4 06:20:13 azza kernel: [   13.155472]  [a03b6000] ?
0xa03b5fff
Aug  4 06:20:13 azza kernel: [   13.156907]  [81002085] ?
do_one_initcall+0x75/0x12c
Aug  4 06:20:13 azza kernel: [   13.158350]  [a03b6000] ?
0xa03b5fff
Aug  4 06:20:13 azza kernel: [   13.159769]  [81073b04] ?
sys_init_module+0x109/0x25b
Aug  4 06:20:13 azza kernel: [   13.161185]  [813464d2] ?
system_call_fastpath+0x16/0x1b
Aug  4 06:20:13 azza kernel: [   13.162810] dump_bug_752881() -
disk_max_parts(disk)=256, (disk-flags  GENHD_FL_NO_PART_SCAN)=0x200
Aug  4 06:20:13 azza kernel: [   13.164301] Pid: 1123, comm: modprobe
Not tainted 3.2.0-amw-fix3+ #1
Aug

This is the patch and it was run with the fix disabled and stack
tracing enabled (
diff --git a/block/genhd.c b/block/genhd.c
index 02e9fca..43d783a 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -1798,3 +1798,29 @@ static void disk_release_events(struct gendisk *disk)
WARN_ON_ONCE(disk-ev  disk-ev-block != 1);
kfree(disk-ev);
 }
+
+
+int bug_752881_dbg;
+static int __init set_bug_752881_dbg(char *s)
+{
+   set_bug_752881_dbg = simple_strtoul(s, NULL, 0);
+
+   return 1;
+}
+__setup(bug_752881_dbg=, set_bug_752881_dbg);
+
+#define BUG_DUMP_STK 1
+#define BUG_GOOD_CODE 2
+
+int dump_bug_752881(struct gendisk *disk)
+{
+if (disk_max_parts(disk) = 1)
+return 0;
+if (bug_752881_dbg  BUG_DUMP_STK) {
+printk(%s() - disk_max_parts(disk)=%d, (disk-flags 
GENHD_FL_NO_PART_SCAN)=%#x\n,
+__func__, disk_max_parts(disk), (disk-flags 
GENHD_FL_NO_PART_SCAN));
+}
+if (bug_752881_dbg  BUG_GOOD_CODE)
+return 1;
+return !(disk-flags  GENHD_FL_NO_PART_SCAN);
+}
diff --git a/include/linux/genhd.h b/include/linux/genhd.h
index 6d18f35..be3ad96 100644
--- a/include/linux/genhd.h
+++ b/include/linux/genhd.h
@@ -237,8 +237,13 @@ static inline int disk_max_parts(struct gendisk *disk)

 static inline bool disk_part_scan_enabled(struct gendisk *disk)
 {
+#if 0
return disk_max_parts(disk)  1 
!(disk-flags  GENHD_FL_NO_PART_SCAN);
+#else
+extern int dump_bug_752881(struct gendisk *disk);
+return dump_bug_752881(disk);
+#endif
 }

 static inline dev_t disk_devt(struct gendisk *disk)


I also suspect that having a blank bluRay in the tray which gives
media errors is important?

Aug  4 06:15:51 azza kernel: [3.793076] generic-usb
0003:1267:0201.0001: input,hidraw0: USB HID v1.00 Mouse [USB Mouse] on
usb-:00:1a.1-1/input0
Aug  4 06:15:51 azza kernel: [3.795362]  sdb: sdb1 sdb2 sdb3 sdb4
Aug  4 06:15:51 azza kernel: [3.795721] sd 4:0:0:0: [sdb] Attached SCSI disk
Aug  4 06:15:51 azza kernel: [3.797081] input: Dell Dell Smart
Card Reader Keyboard as
/devices/pci:00/:00:1a.2/usb8/8-1/8-1:1.0/input/input1
Aug  4 06:15:51 azza kernel: [3.797196] generic-usb
0003:413C:2101.0002: input,hidraw1: USB HID v1.11 Keyboard [Dell Dell
Smart Card Reader Keyboard] on usb-:00:1a.2-1/input0
Aug  4 06:15:51 azza kernel: [3.797286] usbcore: registered new
interface driver usbhid
Aug  4 06:15:51 azza kernel: [3.797331] usbhid: USB HID core driver

Bug#752881: Verified bugfix against kernel v3.2

[Andrew Worsley]

-bd_contains)
+   if (!disk_part_scan_enabled(disk) || bdev != bdev-bd_contains)
return -EINVAL;
if (!capable(CAP_SYS_ADMIN))
return -EACCES;
diff --git a/fs/block_dev.c b/fs/block_dev.c
index ff77262..0bed0d4 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -971,7 +971,7 @@ static void flush_disk(struct block_device *bdev,
bool kill_dirty)

if (!bdev-bd_disk)
return;
-   if (disk_partitionable(bdev-bd_disk))
+   if (disk_part_scan_enabled(bdev-bd_disk))
bdev-bd_invalidated = 1;
 }

diff --git a/include/linux/genhd.h b/include/linux/genhd.h
index 02fa469..6d18f35 100644
--- a/include/linux/genhd.h
+++ b/include/linux/genhd.h
@@ -128,6 +128,7 @@ struct hd_struct {
 #define GENHD_FL_EXT_DEVT  64 /* allow extended devt */
 #define GENHD_FL_NATIVE_CAPACITY   128
 #define GENHD_FL_BLOCK_EVENTS_ON_EXCL_WRITE256
+#define GENHD_FL_NO_PART_SCAN  512

 enum {
DISK_EVENT_MEDIA_CHANGE = 1  0, /* media changed */
@@ -234,9 +235,10 @@ static inline int disk_max_parts(struct gendisk *disk)
return disk-minors;
 }

-static inline bool disk_partitionable(struct gendisk *disk)
+static inline bool disk_part_scan_enabled(struct gendisk *disk)
 {
-   return disk_max_parts(disk)  1;
+   return disk_max_parts(disk)  1 
+   !(disk-flags  GENHD_FL_NO_PART_SCAN);
 }

 static inline dev_t disk_devt(struct gendisk *disk)
From d307a67863bf14f1785f0faa39ef2ad496758e4a Mon Sep 17 00:00:00 2001
From: Andrew Worsley amwors...@gmail.com
Date: Sat, 26 Jul 2014 06:46:53 +1000
Subject: [PATCH] Revert block: add GENHD_FL_NO_PART_SCAN

This reverts commit d27769ec3df1a8de9ca450d2dcd72d1ab259ba32 but keeps the
definition of GENHD_FL_NO_PART_SCAN used by drivers/block/loop.c

 Fix debian bug report #752881 which results in errors like then when access a PCI bus based bluRay drive
...
Jun  7 14:08:36 azza kernel: [569395.478041] end_request: I/O error, dev sr1, sector 0
Jun  7 14:08:36 azza kernel: [569395.481744] sr 6:0:0:0: [sr1] Unhandled sense code
Jun  7 14:08:36 azza kernel: [569395.481746] sr 6:0:0:0: [sr1]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jun  7 14:08:36 azza kernel: [569395.481748] sr 6:0:0:0: [sr1]  Sense Key : Blank Check [current]
Jun  7 14:08:36 azza kernel: [569395.481751] sr 6:0:0:0: [sr1]  Add. Sense: No additional sense information
Jun  7 14:08:36 azza kernel: [569395.481754] sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
...
---
 block/genhd.c |4 ++--
 block/ioctl.c |2 +-
 fs/block_dev.c|2 +-
 include/linux/genhd.h |7 +++
 4 files changed, 7 insertions(+), 8 deletions(-)

diff --git a/block/genhd.c b/block/genhd.c
index 02e9fca..d261b73 100644
--- a/block/genhd.c
+++ b/block/genhd.c
@@ -536,7 +536,7 @@ void register_disk(struct gendisk *disk)
 	disk-slave_dir = kobject_create_and_add(slaves, ddev-kobj);
 
 	/* No minors to use for partitions */
-	if (!disk_part_scan_enabled(disk))
+	if (!disk_partitionable(disk))
 		goto exit;
 
 	/* No such device (e.g., media were just removed) */
@@ -847,7 +847,7 @@ static int show_partition(struct seq_file *seqf, void *v)
 	char buf[BDEVNAME_SIZE];
 
 	/* Don't show non-partitionable removeable devices or empty devices */
-	if (!get_capacity(sgp) || (!disk_max_parts(sgp) 
+	if (!get_capacity(sgp) || (!disk_partitionable(sgp) 
    (sgp-flags  GENHD_FL_REMOVABLE)))
 		return 0;
 	if (sgp-flags  GENHD_FL_SUPPRESS_PARTITION_INFO)
diff --git a/block/ioctl.c b/block/ioctl.c
index ca939fc..5554403 100644
--- a/block/ioctl.c
+++ b/block/ioctl.c
@@ -102,7 +102,7 @@ static int blkdev_reread_part(struct block_device *bdev)
 	struct gendisk *disk = bdev-bd_disk;
 	int res;
 
-	if (!disk_part_scan_enabled(disk) || bdev != bdev-bd_contains)
+	if (!disk_partitionable(disk) || bdev != bdev-bd_contains)
 		return -EINVAL;
 	if (!capable(CAP_SYS_ADMIN))
 		return -EACCES;
diff --git a/fs/block_dev.c b/fs/block_dev.c
index b07f1da..1c44b8d 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -971,7 +971,7 @@ static void flush_disk(struct block_device *bdev, bool kill_dirty)
 
 	if (!bdev-bd_disk)
 		return;
-	if (disk_part_scan_enabled(bdev-bd_disk))
+	if (disk_partitionable(bdev-bd_disk))
 		bdev-bd_invalidated = 1;
 }
 
diff --git a/include/linux/genhd.h b/include/linux/genhd.h
index 6d18f35..886f8ea 100644
--- a/include/linux/genhd.h
+++ b/include/linux/genhd.h
@@ -128,7 +128,7 @@ struct hd_struct {
 #define GENHD_FL_EXT_DEVT			64 /* allow extended devt */
 #define GENHD_FL_NATIVE_CAPACITY		128
 #define GENHD_FL_BLOCK_EVENTS_ON_EXCL_WRITE	256
-#define GENHD_FL_NO_PART_SCAN			512
+#define GENHD_FL_NO_PART_SCAN   512
 
 enum {
 	DISK_EVENT_MEDIA_CHANGE			= 1  0, /* media changed */
@@ -235,10 +235,9 @@ static inline int disk_max_parts(struct gendisk *disk)
 	return disk-minors;
 }
 
-static inline bool disk_part_scan_enabled(struct

Bug#752881: update on re-bisect - with clean builds.

[Andrew Worsley]

Rebuilding the kernels completely cleanly each time has narrowed it
down to a list of changes that sound more plausible.

Still working on building and testing...

Andrew

commit e8b177cedc39b092e423b8cbc687dbf096a1de47
Merge: dfaa2ef d27769e
Author: Jens Axboe jax...@fusionio.com
Date:   Tue Aug 23 20:01:11 2011 +0200

Merge branch 'for-3.2/core' into for-3.2/drivers

commit d27769ec3df1a8de9ca450d2dcd72d1ab259ba32
Author: Tejun Heo t...@kernel.org
Date:   Tue Aug 23 20:01:04 2011 +0200

block: add GENHD_FL_NO_PART_SCAN

There are cases where suppressing partition scan is useful - e.g. for
lo devices and pseudo SATA devices which advertise to be a disk but
get upset on partition scan (some port multiplier control devices show
such behavior).

This patch adds GENHD_FL_NO_PART_SCAN which suppresses partition scan
regardless of the number of possible partitions.  disk_partitionable()
is renamed to disk_part_scan_enabled() as suppressing partition scan
doesn't imply the device can't be partitioned using
BLKPG_ADD/DEL_PARTITION calls from userland.  show_partition() now
directly tests disk_max_parts() to maintain backward-compatibility.

-v2: Updated to make it clear that only partition scan is suppressed
 not partitioning itself as suggested by Kay Sievers.

Signed-off-by: Tejun Heo t...@kernel.org
Cc: Kay Sievers kay.siev...@vrfy.org
Signed-off-by: Jens Axboe jax...@fusionio.com

commit dfaa2ef68e80c378e610e3c8c536f1c239e8d3ef
Author: Lukas Czerner lczer...@redhat.com
Date:   Fri Aug 19 14:50:46 2011 +0200

loop: add discard support for loop devices

This commit adds discard support for loop devices. Discard is usually
supported by SSD and thinly provisioned devices as a method for
reclaiming unused space. This is no different than trying to reclaim
back space which is not used by the file system on the image, but it
still occupies space on the host file system.

We can do the reclamation on file system which does support hole
punching. So when discard request gets to the loop driver we can
translate that to punch a hole to the underlying file, hence reclaim
the free space.

This is very useful for trimming down the size of the image to only what
is really used by the file system on that image. Fstrim may be used for
that purpose.

It has been tested on ext4, xfs and btrfs with the image file systems
ext4, ext3, xfs and btrfs. ext4, or ext6 image on ext4 file system has
some problems but it seems that ext4 punch hole implementation is
somewhat flawed and it is unrelated to this commit.

Also this is a very good method of validating file systems punch hole
implementation.

Note that when encryption is used, discard support is disabled, because
using it might leak some information useful for possible attacker.

Signed-off-by: Lukas Czerner lczer...@redhat.com
Reviewed-by: Jeff Moyer jmo...@redhat.com
Signed-off-by: Jens Axboe jax...@fusionio.com

commit 548ef6cc26ca1c81f19855d57d3fb0f9a7ce3385
Author: Andrew Morton a...@linux-foundation.org
Date:   Fri Aug 19 14:48:28 2011 +0200

nbd-replace-some-printk-with-dev_warn-and-dev_info-checkpatch-fixes

ERROR: code indent should use tabs where possible
#30: FILE: drivers/block/nbd.c:578:
+^Idev_info(disk_to_dev(lo-disk), NBD_DISCONNECT\n);$

total: 1 errors, 0 warnings, 35 lines checked

NOTE: whitespace errors detected, you may wish to use scripts/cleanpatch or
  scripts/cleanfile

./patches/nbd-replace-some-printk-with-dev_warn-and-dev_info.patch
has style problems, please review.

If any of these errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.

Please run checkpatch prior to sending patches

Cc: Paul Clements paul.cleme...@steeleye.com
Cc: WANG Cong amw...@redhat.com
Signed-off-by: Andrew Morton a...@linux-foundation.org
Signed-off-by: Jens Axboe jax...@fusionio.com


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

Bug#752881: Fwd: Bug#752881: Found exact revision that causes problem

[Andrew Worsley]

For got to cc this to the bug...-(

On 21 July 2014 09:29, Ben Hutchings b...@decadent.org.uk wrote:
...

 Assuming that this regression only happened once, we can be fairly
 confident that it happened before
 4c823cc3d568277aa6340d8df6981e34f4c4dee5, but as that is around v3.2-rc1
 it doesn't reduce the range very much. :-(


Thank for looking at this issue. I don't get what is going on here
either but it seemed to reliably cause the problem BUT when I reverted
this change in the v3.2 kernel it still had the fault! (Broke my
heart!).

Then I built the version 8a9c59 (just prior to the bad version) from
scratch and this time it had the fault where as before worked!
 So I think I have to build completely cleanly each time...

So I am doing a git bisect again using  a cleaner way of rebuilding the kernels.

I did compile one on either side of it and it seemed solid. i.e.
rebooting the same kernel reliably results in a failure. I didn't
reboot every kernel but certainly the squeeze one is always good and
the wheezy is almost always bad (sometimes you can partially write a
BluRay before it completely bombs but it always gives these errors on
kernel booting).

One idea was that it might be a kernel configuration dependant because
I had to do make oldconfig and as I switched back and forth between
revisions it might have different configurations. But I just diff'ed
the config file from the last 4 builds and there was *NO* difference
so that should cover good and bad builds.

As I didn't rebuild the last set of kernels from scratch I suspect
this is the  cause of the inconstancies.

I am now trying the bisection again but now doing this each time.
  1. Rebuilding from scratch (make-kpkg clean)
  2. Copying the same config file and doing make oldconfig and always
accepting the default.

So far I have:

git bisect start
# bad: [8a9c594422ecad912d6470888acdee9a1236ad68]
drivers/block/loop.c: emit uevent on auto release
git bisect bad 8a9c594422ecad912d6470888acdee9a1236ad68
# good: [02f8c6aee8df3cdc935e9bdd4f2d020306035dbe] Linux 3.0
git bisect good 02f8c6aee8df3cdc935e9bdd4f2d020306035dbe
# good: [0003230e8200699860f0b10af524dc47bf8aecad] Merge branch
'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6
git bisect good 0003230e8200699860f0b10af524dc47bf8aecad
# good: [206d440f64030b6425841bf7cb38e26a5ea0c382] xfs: Fix build
breakage in xfs_iops.c when CONFIG_FS_POSIX_ACL is not set
git bisect good 206d440f64030b6425841bf7cb38e26a5ea0c382
# skip: [c11abbbaa3252875c5740a6880b9a1a6f1e2a870] Merge branch
'slub/lockless' of
git://git.kernel.org/pub/scm/linux/kernel/git/penberg/slab-2.6
git bisect skip c11abbbaa3252875c5740a6880b9a1a6f1e2a870

The last skip because I got compile errors.
...
arch/x86/built-in.o: In function `atomic_read':
/movies3/work/linux/arch/x86/include/asm/atomic.h:25: undefined
reference to `__tracepoint_xen_cpu_write_gdt_entry'
...
Actually I couldn't build the squeeze kernel under wheezy (lots of
problems) so I was building that under the squeeze in a virtual
machine.

This is a real annoying bug because I have to build so many kernels
and hit compile problems but I will crush it.
Suggestions on improving this debug plan would be much welcomed.

Andrew


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

Bug#752881: Found exact revision that causes problem

[Andrew Worsley]

It looks innocent enough - but I have bisected it down to with (bad)
and just before (good)...

4c823cc3d568277aa6340d8df6981e34f4c4dee5 is the first bad commit

* commit 4c823cc
| Author: Ayan George a...@ayan.net
| Date:   Wed Sep 21 10:02:13 2011 +0200
|
| drivers/block/loop.c: remove unnecessary bdev argument from loop_clr_fd()
|
| If the loop device is associated (lo-lo_state == Lo_bound), it will have
| a valid bdev pointed to by lo-lo_device.  There is no reason to ever pass
| an additional block_device pointer.
|
| Signed-off-by: Ayan George ayan.geo...@canonical.com
| Cc: Phillip Susi ps...@cfl.rr.com
| Cc: Jens Axboe ax...@kernel.dk
| Signed-off-by: Andrew Morton a...@google.com
| Signed-off-by: Jens Axboe ax...@kernel.dk
|
| M drivers/block/loop.c

% git diff 4c823cc3d568277aa6340d8df6981e34f4c4dee5~
4c823cc3d568277aa6340d8df6981e34f4c4dee5
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index c2ce03c..9b2f5d3 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1051,10 +1051,11 @@ loop_init_xfer(struct loop_device *lo, struct
loop_func_table *xfer,
return err;
 }

-static int loop_clr_fd(struct loop_device *lo, struct block_device *bdev)
+static int loop_clr_fd(struct loop_device *lo)
 {
struct file *filp = lo-lo_backing_file;
gfp_t gfp = lo-old_gfp_mask;
+   struct block_device *bdev = lo-lo_device;

if (lo-lo_state != Lo_bound)
return -ENXIO;
@@ -1372,7 +1373,7 @@ static int lo_ioctl(struct block_device *bdev,
fmode_t mode,
break;
case LOOP_CLR_FD:
/* loop_clr_fd would have unlocked lo_ctl_mutex on success */
-   err = loop_clr_fd(lo, bdev);
+   err = loop_clr_fd(lo);
if (!err)
goto out_unlocked;
break;
@@ -1583,7 +1584,7 @@ static int lo_release(struct gendisk *disk, fmode_t mode)
 * In autoclear mode, stop the loop thread
 * and remove configuration after last close.
 */
-   err = loop_clr_fd(lo, lo-lo_device);
+   err = loop_clr_fd(lo);
if (!err)
goto out_unlocked;
} else {


--
   Full git bisection history:
git bisect start
# good: [4c37b233616542536c75d20355d38d1065842103] fixes so can build
under wheezy
git bisect good 4c37b233616542536c75d20355d38d1065842103
# bad: [805a6af8dba5dfdd35ec35dc52ec0122400b2610] Linux 3.2
git bisect bad 805a6af8dba5dfdd35ec35dc52ec0122400b2610
# good: [22763c5cf3690a681551162c15d34d935308c8d7] Linux 2.6.32
git bisect good 22763c5cf3690a681551162c15d34d935308c8d7
# good: [8c4877a4128e7931077b024a891a4b284d8756a3] ehea: Use the
standard logging functions
git bisect good 8c4877a4128e7931077b024a891a4b284d8756a3
# good: [1d0738ea48829cb234fcaba830eef3461985ff44] ARM: mach-shmobile:
Use SCIFA and SCIFB port types on sh7377
git bisect good 1d0738ea48829cb234fcaba830eef3461985ff44
# good: [03b7898d300de62078cc130fbc83b84b1d1e0f8d] ARM: perf: move
active_events into struct arm_pmu
git bisect good 03b7898d300de62078cc130fbc83b84b1d1e0f8d
# good: [0e59e7e7feb5a12938fbf9135147eeda3238c6c4] Merge branch
'next-rebase' of
git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci
git bisect good 0e59e7e7feb5a12938fbf9135147eeda3238c6c4
# good: [1046a2c428bedd64c960dcfd0c57cc69a82fea2f] Merge branch
'v4l_for_linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
git bisect good 1046a2c428bedd64c960dcfd0c57cc69a82fea2f
# bad: [5b34b08996decc53a993287282e2cd42b90e02f7] Merge branch 'fixes'
of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
git bisect bad 5b34b08996decc53a993287282e2cd42b90e02f7
# bad: [32aaeffbd4a7457bf2f7448b33b5946ff2a960eb] Merge branch
'modsplit-Oct31_2011' of
git://git.kernel.org/pub/scm/linux/kernel/git/paulg/linux
git bisect bad 32aaeffbd4a7457bf2f7448b33b5946ff2a960eb
# bad: [ec773e99ab4abce07b1ae23117179c2861831964] Merge branch 'fixes'
of http://ftp.arm.linux.org.uk/pub/linux/arm/kernel/git-cur/linux-2.6-arm
git bisect bad ec773e99ab4abce07b1ae23117179c2861831964
# bad: [00411ee9308e4b5f4b04caaa01685f955e259373] watchdog: Convert
wm831x driver to watchdog core
git bisect bad 00411ee9308e4b5f4b04caaa01685f955e259373
# good: [b4fdcb02f1e39c27058a885905bd0277370ba441] Merge branch
'for-3.2/core' of git://git.kernel.dk/linux-block
git bisect good b4fdcb02f1e39c27058a885905bd0277370ba441
# good: [51ddf31da16b1ab9da861eafedad6d263faf4388] ARM: SAMSUNG:
Remove Samsung specific enum type for dma direction
git bisect good 51ddf31da16b1ab9da861eafedad6d263faf4388
# bad: [b8d8bdfe31a67981bbc398a4886ccc67aff521d5] Merge branch
'stable/for-jens-3.2' of git://oss.oracle.com/git/kwilk/xen into
for-3.2/drivers
git bisect bad b8d8bdfe31a67981bbc398a4886ccc67aff521d5
# good: [8a9c594422ecad912d6470888acdee9a1236ad68]
drivers/block/loop.c: emit uevent on auto release
git bisect good 

Bug#752881: Shorter gitsect list

[Andrew Worsley]

It appears some where between linux 3.1.0-rc4 and 3.1.0


More detailed git log  below:


git bisect view --pretty=oneline --abbrev-commit --graph
* 00411ee watchdog: Convert wm831x driver to watchdog core
* 25dc46e watchdog: s3c2410: convert to use the watchdog framework
* 74cd4c6 Documentation: watchdog: add guide how to convert drivers to
new framework
* deb9197 watchdog: iTCO_wdt.c - problems with newer hardware due to
SMI clearing
* c63b6d0 watchdog: Add WDIOC_GETTIMELEFT ioctl support to w83627
watchdog driver
* 86b5912 watchdog: irq: Remove IRQF_DISABLED
* 47bfd05 watchdog: Octeon: Mark octeon_wdt interrupt as IRQF_NO_THREAD
* cef153a watchdog: sc520_wdt: Remove unnecessary cast.
* dc822e5 ARM: EXYNOS4: Fix the merge conflict
* 5c8a0fb VFS: fix statfs() automounter semantics regression
*   fba9569 Merge branch 'next' of git://git.infradead.org/users/vkoul/slave-dma
|\
| * 4598fc2 dmaengine: mid_dma: mask_peripheral_interrupt only when dmac is idle
| * 2389d67 dmaengine/ep93xx_dma: add module.h include
| * 01631243d pch_dma: Reduce wasting memory
| * c43f150 pch_dma: Fix suspend issue
| * f80befe dma/timberdale: free_irq() on an error path
| * 7a1cd9a dma: shdma: transfer based runtime PM
| * b4dae6e dmaengine: shdma: protect against the IRQ handler
| * 0745c9a Merge branch 'samsung_dma' into next
| * f8de8f4 dmaengine i.MX DMA/SDMA: add missing include of linux/module.h
| * 46389470 dmaengine: delete redundant chan_id and chancnt
initialization in dma drivers
| * c120564 dmaengine/amba-pl08x: Check txd-llis_va before freeing dma_pool
| * b7f69d9 dmaengine/amba-pl08x: Add support for sg len greater than
one for slave transfers
| * 937bb6e serial: sh-sci: don't filter on DMA device, use only channel ID
* 3d0a8d1 Merge branch 'for-3.2/drivers' of git://git.kernel.dk/linux-block
* a0eda62 virtio-blk: use ida to allocate disk index
* c4853ef hpsa: add small delay when using PCI Power Management to
reset for kump
* ab5dbeb cciss: add small delay when using PCI Power Management to
reset for kump
*   b8d8bdf Merge branch 'stable/for-jens-3.2' of
git://oss.oracle.com/git/kwilk/xen into for-3.2/drivers
|\
| * 6927d92 xen/blkback: Fix two races in the handling of barrier requests.
| * dda1852 xen/blkback: Check for proper operation.
| * 64391b2 xen/blkback: Fix the inhibition to map pages when
discarding sector ranges.
| * 5c62cb4 xen/blkback: Report VBD_WSECT (wr_sect) properly.
| * 29bde09 xen/blkback: Support 'feature-barrier' aka old-style
BARRIER requests.
| * 469738e xen-blkfront: plug device number leak in xlblk_init() error path
| * d11e615 xen-blkfront: If no barrier or flush is supported, use
invalid operation.
| * 8e6dc6f xen-blkback: use kzalloc() in favor of kmalloc()+memset()
| * c555aab xen-blkback: fixed indentation and comments
| * 69ef68c xen-blkfront: fix a deadlock while handling discard response
| * ed30bf3 xen-blkfront: Handle discard requests.
| * b3cb0d6 xen-blkback: Implement discard requests ('feature-discard')
| * 32a8d26 xen-blkfront: add BLKIF_OP_DISCARD and discard request struct
* 4c823cc drivers/block/loop.c: remove unnecessary bdev argument from
loop_clr_fd()
* 8a9c594 drivers/block/loop.c: emit uevent on auto release
* 5a3a76e drivers/block/cpqarray.c: use pci_dev-revision
* e03c8dd loop: always allow userspace partitions and optionally
support automatic scanning
*   e8b177c Merge branch 'for-3.2/core' into for-3.2/drivers
|\
| * d27769e block: add GENHD_FL_NO_PART_SCAN
* dfaa2ef loop: add discard support for loop devices
* 548ef6c nbd-replace-some-printk-with-dev_warn-and-dev_info-checkpatch-fixes
* 5eedf54 nbd: replace some printk with dev_warn() and dev_info()
* 7742ce4 nbd: lower the loglevel of an error message
* 7f1b90f nbd: replace printk KERN_ERR with dev_err()
* 1695b87 nbd: replace sysfs_create_file() with device_create_file()
* 25ac0c2 nbd: use task_pid_nr() to get current pid
* f963d27 cciss: add transport mode attribute to sys
* 1304953 cciss: Adds simple mode functionality


git bisect start
# good: [4c37b233616542536c75d20355d38d1065842103] fixes so can build
under wheezy
git bisect good 4c37b233616542536c75d20355d38d1065842103
# bad: [805a6af8dba5dfdd35ec35dc52ec0122400b2610] Linux 3.2
git bisect bad 805a6af8dba5dfdd35ec35dc52ec0122400b2610
# good: [22763c5cf3690a681551162c15d34d935308c8d7] Linux 2.6.32
git bisect good 22763c5cf3690a681551162c15d34d935308c8d7
# good: [8c4877a4128e7931077b024a891a4b284d8756a3] ehea: Use the
standard logging functions
git bisect good 8c4877a4128e7931077b024a891a4b284d8756a3
# good: [1d0738ea48829cb234fcaba830eef3461985ff44] ARM: mach-shmobile:
Use SCIFA and SCIFB port types on sh7377
git bisect good 1d0738ea48829cb234fcaba830eef3461985ff44
# good: [03b7898d300de62078cc130fbc83b84b1d1e0f8d] ARM: perf: move
active_events into struct arm_pmu
git bisect good 03b7898d300de62078cc130fbc83b84b1d1e0f8d
# good: [0e59e7e7feb5a12938fbf9135147eeda3238c6c4] Merge branch
'next-rebase' of

Bug#752881: Another git bisection

[Andrew Worsley]

Identified Fault within 7 changes
commit b8d8bdfe31a67981bbc398a4886ccc67aff521d5
Merge: 4c823cc 6927d92
Author: Jens Axboe ax...@kernel.dk
Date:   Thu Oct 20 15:10:59 2011 +0200

Merge branch 'stable/for-jens-3.2' of git://oss.oracle.com/git/kwilk/xen 
into for-3.2/drivers

commit 6927d92091df2848fc0e6a693a017d4b2df549c2
Author: Konrad Rzeszutek Wilk konrad.w...@oracle.com
Date:   Mon Oct 17 14:27:48 2011 -0400

xen/blkback: Fix two races in the handling of barrier requests.

There are two windows of opportunity to cause a race when
processing a barrier request. This patch fixes this.

Signed-off-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com

commit dda1852802a6cc6fdecb9021e491b2de680c76b9
Author: Konrad Rzeszutek Wilk konrad.w...@oracle.com
Date:   Fri Oct 14 12:13:05 2011 -0400

xen/blkback: Check for proper operation.

The patch titled: xen/blkback: Fix the inhibition to map pages
when discarding sector ranges. had the right idea except that
it used the wrong comparison operator. It had == instead of !=.

This fixes the bug where all (except discard) operations would
have been ignored.

Signed-off-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com

commit 64391b2536ca92f9c589b2bfeaca3954896fe057
Author: Konrad Rzeszutek Wilk konrad.w...@oracle.com
Date:   Mon Oct 10 00:47:49 2011 -0400

xen/blkback: Fix the inhibition to map pages when discarding sector ranges.

The 'operation' parameters are the ones provided to the bio layer while
the req-operation are the ones passed in between the backend and
frontend. We used the wrong 'operation' value to squash the
call to map pages when processing the discard operation resulting
in an hypercall that did nothing. Lets guard against going in the
mapping function by checking for the proper operation type.

CC: Li Dongyang lidongy...@novell.com
Signed-off-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com

commit 5c62cb48602dba95159c81ffeca179d3852e25be
Author: Konrad Rzeszutek Wilk konrad.w...@oracle.com
Date:   Mon Oct 10 12:33:21 2011 -0400

xen/blkback: Report VBD_WSECT (wr_sect) properly.

We did not increment the amount of sectors written to disk
b/c we tested for the == WRITE which is incorrect - as the
operations are more of WRITE_FLUSH, WRITE_ODIRECT. This patch
fixes it by doing a  WRITE check.

CC: sta...@kernel.org
Reported-by: Andy Burns xen.li...@burns.me.uk
Suggested-by: Ian Campbell ian.campb...@citrix.com
Signed-off-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com

commit 29bde093787f3bdf7b9b4270ada6be7c8076e36b
Author: Konrad Rzeszutek Wilk konrad.w...@oracle.com
Date:   Mon Oct 10 00:42:22 2011 -0400

xen/blkback: Support 'feature-barrier' aka old-style BARRIER requests.

We emulate the barrier requests by draining the outstanding bio's
and then sending the WRITE_FLUSH command. To drain the I/Os
we use the refcnt that is used during disconnect to wait for all
the I/Os before disconnecting from the frontend. We latch on its
value and if it reaches either the threshold for disconnect or when
there are no more outstanding I/Os, then we have drained all I/Os.

Suggested-by: Christopher Hellwig h...@infradead.org
Signed-off-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com

commit 469738e675524b6aa029ecd46bdda3f878b12eff
Author: Laszlo Ersek ler...@redhat.com
Date:   Fri Oct 7 21:34:38 2011 +0200

xen-blkfront: plug device number leak in xlblk_init() error path

... though after a failed xenbus_register_frontend() all may be lost.

Acked-by: Ian Campbell ian.campb...@citrix.com
Signed-off-by: Laszlo Ersek ler...@redhat.com
Signed-off-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com

commit d11e6158307bed3f178399a4e6216eec67d16200
Author: Konrad Rzeszutek Wilk konrad.w...@oracle.com
Date:   Fri Sep 16 15:15:14 2011 -0400

xen-blkfront: If no barrier or flush is supported, use invalid operation.

Guard against issuing BLKIF_OP_WRITE_BARRIER or BLKIF_OP_FLUSH_CACHE
by checking whether we successfully negotiated with the backend.
The negotiation with the backend also sets the q-flush_flags which
fortunately for us is also used when submitting an bio to us. If
we don't support barriers or flushes it would be set to zero so
we should never end up having to deal with REQ_FLUSH | REQ_FUA.

However, other third party implementations of __make_request that
might be stacked on top of us might not be so smart, so lets fix this up.

Acked-by: Jan Beulich jbeul...@suse.com
Signed-off-by: Konrad Rzeszutek Wilk konrad.w...@oracle.com

commit 8e6dc6fe51957116d363204a725c1262b4b78e19
Author: Jan Beulich jbeul...@suse.com
Date:   Fri Sep 16 08:38:09 2011 +0100

xen-blkback: use kzalloc() in favor of kmalloc()+memset()

This fixes the problem of three of those four memset()-s 

Bug#752881:

[Andrew Worsley]

Hi I've done some git bisection on this problem and cut it down to a 1000 revs:

git bisect log
git bisect start
# good: [4c37b233616542536c75d20355d38d1065842103] fixes so can build
under wheezy
git bisect good 4c37b233616542536c75d20355d38d1065842103
# bad: [805a6af8dba5dfdd35ec35dc52ec0122400b2610] Linux 3.2
git bisect bad 805a6af8dba5dfdd35ec35dc52ec0122400b2610
# good: [22763c5cf3690a681551162c15d34d935308c8d7] Linux 2.6.32
git bisect good 22763c5cf3690a681551162c15d34d935308c8d7
# good: [8c4877a4128e7931077b024a891a4b284d8756a3] ehea: Use the
standard logging functions
git bisect good 8c4877a4128e7931077b024a891a4b284d8756a3
# good: [1d0738ea48829cb234fcaba830eef3461985ff44] ARM: mach-shmobile:
Use SCIFA and SCIFB port types on sh7377
git bisect good 1d0738ea48829cb234fcaba830eef3461985ff44
# good: [03b7898d300de62078cc130fbc83b84b1d1e0f8d] ARM: perf: move
active_events into struct arm_pmu
git bisect good 03b7898d300de62078cc130fbc83b84b1d1e0f8d
# good: [0e59e7e7feb5a12938fbf9135147eeda3238c6c4] Merge branch
'next-rebase' of
git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/pci
git bisect good 0e59e7e7feb5a12938fbf9135147eeda3238c6c4
# good: [1046a2c428bedd64c960dcfd0c57cc69a82fea2f] Merge branch
'v4l_for_linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
git bisect good 1046a2c428bedd64c960dcfd0c57cc69a82fea2f
# bad: [5b34b08996decc53a993287282e2cd42b90e02f7] Merge branch 'fixes'
of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc
git bisect bad 5b34b08996decc53a993287282e2cd42b90e02f7


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

Bug#752881: linux-image-3.2.0-4-amd64: bluRay writer can't write under wheezy kernel (I/O error: Unhandled sense code) but ok under squeeze

[Andrew Worsley andrew.worsley]

Package: src:linux
Version: 3.2.57-3+deb7u2
Severity: normal

Dear Maintainer,

   Under this linux-image-3.2.0-4-amd64 kernel my blu Ray writer [sr1] has 
severe problems so that I can not writer a Blu Ray with it.
But it writes perfectly under the older squeeze linux-image-2.6.32-5-amd64 
kernel. This is how I presently work around the problem (boot the
older kernel). It produces endless errors of the form:

Jun  7 14:08:36 azza kernel: [569395.478041] end_request: I/O error, dev sr1, 
sector 0
Jun  7 14:08:36 azza kernel: [569395.481744] sr 6:0:0:0: [sr1] Unhandled sense 
code
Jun  7 14:08:36 azza kernel: [569395.481746] sr 6:0:0:0: [sr1]  Result: 
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Jun  7 14:08:36 azza kernel: [569395.481748] sr 6:0:0:0: [sr1]  Sense Key : 
Blank Check [current] 
Jun  7 14:08:36 azza kernel: [569395.481751] sr 6:0:0:0: [sr1]  Add. Sense: No 
additional sense information
Jun  7 14:08:36 azza kernel: [569395.481754] sr 6:0:0:0: [sr1] CDB: Read(10): 
28 00 00 00 00 00 00 00 01 00
...

   Googling around I hit upon this 
http://forums.debian.net/viewtopic.php?f=7t=111795start=30 which references 
https://lkml.org/lkml/2014/5/9/363
   and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701201
   which suggested : libata.atapi_passthru16=0 is needed by some hardware

   I tried this which allowed me to write about half a bluRay and then it 
failed - leaving a half written unusable disc !

   Would love a fix to avoid having to flick back to the older kernel which is 
really inconvient to others.


   Thinking about trying to build kernels back to 2.6.32 and seeing where the 
break is - but 2.6.32 appears to have *LOTS* of problems compiling with the 
wheezy
   set up (gcc 4.7.2)...

   Perhaps Jessie might be a better direction - but really want to run a stable 
kernel on this machine as it is used by other people.

   Andrew


-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.57-3+deb7u2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=c5c1b15a-a6fc-11e0-a2f4-001e8c7db70d ro nmi_watchdog=1 
libata.atapi_passthru16=0

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[   30.012531] sr 6:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   30.014528] sr 6:0:0:0: [sr1]  Add. Sense: No additional sense information
[   30.016534] sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[   30.018571] end_request: I/O error, dev sr1, sector 0
[   30.029441] sr 6:0:0:0: [sr1] Unhandled sense code
[   30.031425] sr 6:0:0:0: [sr1]  Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[   30.033432] sr 6:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   30.035432] sr 6:0:0:0: [sr1]  Add. Sense: No additional sense information
[   30.037440] sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[   30.039476] end_request: I/O error, dev sr1, sector 0
[   30.050342] sr 6:0:0:0: [sr1] Unhandled sense code
[   30.052329] sr 6:0:0:0: [sr1]  Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[   30.054327] sr 6:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   30.056332] sr 6:0:0:0: [sr1]  Add. Sense: No additional sense information
[   30.058334] sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[   30.060376] end_request: I/O error, dev sr1, sector 0
[   30.071236] sr 6:0:0:0: [sr1] Unhandled sense code
[   30.073223] sr 6:0:0:0: [sr1]  Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[   30.075221] sr 6:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   30.077225] sr 6:0:0:0: [sr1]  Add. Sense: No additional sense information
[   30.079223] sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[   30.081266] end_request: I/O error, dev sr1, sector 0
[   30.092129] sr 6:0:0:0: [sr1] Unhandled sense code
[   30.094107] sr 6:0:0:0: [sr1]  Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[   30.096117] sr 6:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   30.098117] sr 6:0:0:0: [sr1]  Add. Sense: No additional sense information
[   30.100123] sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[   30.102159] end_request: I/O error, dev sr1, sector 0
[   30.113029] sr 6:0:0:0: [sr1] Unhandled sense code
[   30.115015] sr 6:0:0:0: [sr1]  Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[   30.117024] sr 6:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   30.119024] sr 6:0:0:0: [sr1]  Add. Sense: No additional sense information
[   30.121029] sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
[   30.123067] end_request: I/O error, dev sr1, sector 0
[   30.133933] sr 6:0:0:0: [sr1] Unhandled sense code
[   30.135916] sr 6:0:0:0: [sr1]  Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[   30.137924] sr 6:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   30.139921] sr 6:0:0:0: [sr1]  Add. Sense: No additional sense information
[   30.141927] sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 

Bug#634937: cups: Seen this in my messages log

[Andrew Worsley andrew.worsley]

Package: cups
Version: 1.5.3-5+deb7u1
Followup-For: Bug #634937

Dear Maintainer,

  I wasn't doing anything particular and noticed that the cups daemon was no 
longer running when a print job failed
  to appear. I grep'ed the messages log and got this single line:

   grep cups /var/log/messages.1
Jan 25 11:53:28 azza kernel: [3067672.112302] cupsd[17528]: segfault at 220 ip 
7ffbffc0c1b3 sp 7fff5544e818
error 4 in libavahi-common.so.3.5.3[7ffbffc07000+c000]

  Restarting cupsd via 
service cups restart

  starts printing happening again. But the print job needed to be re-submitted.


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

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

Versions of packages cups depends on:
ii  adduser3.113+nmu3
ii  bc 1.06.95-2+b1
ii  cups-client1.5.3-5+deb7u1
ii  cups-common1.5.3-5+deb7u1
ii  cups-filters   1.0.18-2.1
ii  cups-ppdc  1.5.3-5+deb7u1
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg   1.16.12
ii  ghostscript9.05~dfsg-6.3+deb7u1
ii  libavahi-client3   0.6.31-2
ii  libavahi-common3   0.6.31-2
ii  libc-bin   2.13-38
ii  libc6  2.13-38
ii  libcups2   1.5.3-5+deb7u1
ii  libcupscgi11.5.3-5+deb7u1
ii  libcupsimage2  1.5.3-5+deb7u1
ii  libcupsmime1   1.5.3-5+deb7u1
ii  libcupsppdc1   1.5.3-5+deb7u1
ii  libdbus-1-31.6.8-1+deb7u1
ii  libgcc11:4.7.2-5
ii  libgnutls262.12.20-7
ii  libgssapi-krb5-2   1.10.1+dfsg-5+deb7u1
ii  libkrb5-3  1.10.1+dfsg-5+deb7u1
ii  libldap-2.4-2  2.4.31-1+nmu2
ii  libpam0g   1.1.3-7.1
ii  libpaper1  1.1.24+nmu2
ii  libslp11.2.1-9
ii  libstdc++6 4.7.2-5
ii  libusb-1.0-0   2:1.0.11-1
ii  lsb-base   4.1+Debian8+deb7u1
ii  poppler-utils  0.18.4-6
ii  procps 1:3.3.3-3
ii  ssl-cert   1.0.32

Versions of packages cups recommends:
ii  avahi-daemon   0.6.31-2
ii  colord 0.1.21-1
ii  foomatic-filters   4.0.17-1
ii  ghostscript-cups   9.05~dfsg-6.3+deb7u1
ii  printer-driver-gutenprint  5.2.9-1

Versions of packages cups suggests:
ii  cups-bsd   1.5.3-5+deb7u1
pn  cups-pdf   none
ii  foomatic-db20120523-1
ii  hplip  3.12.6-3.1+deb7u1
ii  printer-driver-hpcups  3.12.6-3.1+deb7u1
ii  smbclient  2:3.6.6-6+deb7u2
ii  udev   175-7.2

-- debconf information:
  cupsys/raw-print: true
  cupsys/backend: ipp, ipp14, lpd, socket, usb


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

Bug#714234: dump: restore #157 dump fails to restore incremental if directory was removed

[Andrew Worsley]

Package: dump
Version: 0.4b43-1
Severity: important

Needed to test my restores on squeeze and hit this problem:
http://sourceforge.net/p/dump/bugs/157/

Full dump ok - but incremental's appear to be stuffed up by this.
Nasty thing is you don't know it until you need it. This bug is still
current i.e. as far as
I know any one uses dump/restore on debian since squeeze or later may
hit this problem when they restore.

If you do a restore -x instead of -r it runs - but complains about
files existing / not existing - so I am not sure if you get back
exactly what you had...

I tried the reported work around of going back to debian lenny version
0.4b41 and I get a lot of complaints about bad entry -
Possibly - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574469

What is worse is it appears the maintainer has no interest in fixing these?


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

Bug#654867: This other bug report trail might point to the upstream fix for the problem

[Andrew Worsley]

https://bugs.launchpad.net/linaro-image-tools/+bug/697684


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

Bug#697263: photon: Gets ZeroDivisionError: float division

[Andrew Worsley andrew.worsley]

Package: photon
Version: 0.4.6-1.1
Severity: important
Tags: patch


Following Command generates an exception which stops the program working:

photon --sizelist=0,1600x1200,800x600 --thumbsize=320x240 -o /backup/amw/albums 
/tmp/NZ
Traceback (most recent call last):
  File /home/amw/bin/photon, line 2290, in module
main()
  File /home/amw/bin/photon, line 298, in main
process_directory(path,)
  File /home/amw/bin/photon, line 440, in process_directory
make_image_html(relativepath,directories_list, images_list)
  File /home/amw/bin/photon, line 905, in make_image_html
fill_image_html_exif_window(namespace, image)
  File /home/amw/bin/photon, line 1252, in fill_image_html_exif_window
exif_value = exif_resolv_ratio( imageinfo['exif'][exif_key] )
  File /home/amw/bin/photon, line 1231, in exif_resolv_ratio
return float(m.group(1)) / float(m.group(2))
ZeroDivisionError: float division

The m.group(2) is 0 - I don't know the image which does it or exactly why but 
I hacked the code to
detect it and use the result 1.0 and it appears to work ok?

--- /usr/bin/photon 2008-07-19 01:51:16.0 +1000
+++ /home/amw/bin/photon2013-01-03 16:56:33.0 +1100
@@ -1227,6 +1227,9 @@
 ratio = ratio_of_ifdtag
   m = re.search(^(\d+)/(\d+)$, ratio)
   if m:
+if m.group(2) == 0:
+   print m.group(2)=, m.group(2), \n
+   return 1.0
 return float(m.group(1)) / float(m.group(2))
   else:
 return float(ratio)


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

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

Versions of packages photon depends on:
ii  python  2.6.6-3+squeeze7 interactive high-level object-orie
ii  python-central  0.6.16+nmu1  register and build utility for Pyt
ii  python-imaging  1.1.7-2  Python Imaging Library

Versions of packages photon recommends:
ii  dcraw  8.99-1+b1 decode raw digital camera images
ii  gimp   2.6.10-1+squeeze3 The GNU Image Manipulation Program

photon 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#692731: Debian wheezy CD1 beta3 installation on Mac Pro Retina

[Andrew Worsley]

Package: installation-reports

Boot method: CD in an external CD drive
Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/amd64/jigdo-cd/
- CD1 used jigdo to build it
Date: 8th Nov 2012

Machine: Apple Inc. MacBookPro10,1/Mac-C3EC7CD22292981F, BIOS
MBP101.88Z.00EE.B00.1205101839 05/10/2012
Processor: Intel(R) Core(TM) i7-3615QM CPU @ 2.30GHz stepping 09
Memory: 16Gb
Partitions:
df  -T
Filesystem Type  Size
Used Avail Use% Mounted on
rootfs rootfs118G
 98G   15G  88% /
udev   devtmpfs   10M
   0   10M   0% /dev
tmpfs  tmpfs 1.6G
452K  1.6G   1% /run
/dev/disk/by-uuid/9ad44c06-106c-40c8-b1fa-ff72043d760b ext4  118G
 98G   15G  88% /
tmpfs  tmpfs 5.0M
   0  5.0M   0% /run/lock
tmpfs  tmpfs 7.9G
   0  7.9G   0% /run/shm
tmpfs  tmpfs 7.9G
2.9M  7.9G   1% /tmp

sudo parted /dev/sda print
Model: ATA APPLE SSD SM256E (scsi)
Disk /dev/sda: 251GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt

Number  Start   End SizeFile system  Name  Flags
 1  20.5kB  210MB   210MB   fat32EFI system partition  boot
 2  210MB   99.2GB  99.0GB  hfs+ Customer
 3  100GB   101GB   650MB   hfs+ Recovery HD
 4  101GB   112GB   10.7GB  ext4
 5  112GB   123GB   11.6GB  ext4
 6  123GB   251GB   128GB   ext4

Output of lspci -knn (or lspci -nn):
lspci -knn
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor
DRAM Controller [8086:0154] (rev 09)
Subsystem: Apple Inc. Device [106b:00f7]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor PCI Express Root Port [8086:0151] (rev 09)
Kernel driver in use: pcieport
00:01.1 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor PCI Express Root Port [8086:0155] (rev 09)
Kernel driver in use: pcieport
00:01.2 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor PCI Express Root Port [8086:0159] (rev 09)
Kernel driver in use: pcieport
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7
Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev
04)
Subsystem: Intel Corporation Device [8086:7270]
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series
Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series
Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series
Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation HM77 Express Chipset LPC
Controller [8086:1e57] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset
Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset
Family SMBus Controller [8086:1e22] (rev 04)
Subsystem: Intel Corporation Device [8086:7270]
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device
[10de:0fd5] (rev a1)
Subsystem: Apple Inc. Device [106b:00f2]
01:00.1 Audio device [0403]: NVIDIA Corporation Device [10de:0e1b] (rev a1)
Subsystem: Apple Inc. Device [106b:00f2]
Kernel driver in use: snd_hda_intel
03:00.0 Ethernet controller [0200]: Broadcom Corporation Device
[14e4:16a3] (rev 10)
Subsystem: Broadcom Corporation Device [14e4:16b4]
03:00.1 SD Host controller [0805]: Broadcom Corporation NetXtreme
BCM57765 Memory Card Reader [14e4:16bc] (rev 10)
Subsystem: Broadcom Corporation 

Bug#621717: debirf: unpacking coreutils - ../../src/archives.c:823: tarobject: Assertion `r == stab.st_size' failed

[Andrew Worsley]

Package: debirf
Version: 0.27-1
Severity: important


 Simplest possible usage - just build minimal system:
mkdir ~/debirf
cd ~/debirf
tar xzf /usr/share/doc/debirf/example-profiles/minimal.tgz
debirf make minimal
...
I: Unpacking coreutils...
W: Failure while unpacking required packages.  This will be attempted up to 
five times.
I: Unpacking libattr1...
I: Unpacking base-files...
I: Unpacking base-passwd...
I: Unpacking bash...
I: Unpacking binutils...
I: Unpacking libbz2-1.0...
I: Unpacking coreutils...
W: Failure while unpacking required packages.  This will be attempted up to 
five times.
debirf(0)% ls -a

   amw:12:40PM
.  ..  minimal
debirf(0)%  tail minimal/root/debootstrap/debootstrap.log   

   amw:12:41PM
  libattr1 is unpacked, but has never been configured.
dpkg: warning: ignoring pre-dependency problem!
dpkg: regarding .../coreutils_8.5-1_amd64.deb containing coreutils, 
pre-dependency problem:
 coreutils pre-depends on libselinux1 (= 1.32)
  libselinux1 is unpacked, but has never been configured.
dpkg: warning: ignoring pre-dependency problem!
Preparing to replace coreutils 8.5-1 (using .../coreutils_8.5-1_amd64.deb) ...
Unpacking replacement coreutils ...
dpkg: ../../src/archives.c:823: tarobject: Assertion `r == stab.st_size' failed.
Aborted


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

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

Versions of packages debirf depends on:
ii  apt  0.8.10.3Advanced front-end for dpkg
ii  busybox  1:1.17.1-8  Tiny utilities for small and embed
ii  cpio 2.11-4  GNU cpio -- a program to manage ar
ii  debootstrap  1.0.26+squeeze1 Bootstrap a basic Debian system
ii  fakechroot   2.9-1.1 gives a fake chroot environment
ii  fakeroot 1.14.4-1Gives a fake root environment
ii  klibc-utils  1.5.20-1small utilities built with klibc f

Versions of packages debirf recommends:
ii  genisoimage 9:1.1.11-1   Creates ISO-9660 CD-ROM filesystem
ii  grub-common 1.98+20100804-14 GRand Unified Bootloader, version 

debirf 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