Bug#779370:

2015-02-27 Thread email . bug
With udev rules that call a script to applies the apm_on_ac or apm_on_battery settings accordingly, the systemd resume could be handled with a unit file like this: [Unit] Description=Trigger all block device udev rules on resume to re-apply non-permanent device settings (e.g. smartctl and hdpar

Bug#779370: hdparm + systemd: old apm/pm-utils hooks not working/migrated

2015-02-27 Thread email . bug
Package: hdparm Severity: serious The apm/pm-utils suspend/resume functionalities, provided by shipping the files 20hdparm and 95hdparm-apm scripts, do not work with systemd. (missing systemd unit files) To allow setting defaults I would suggest to support wildcards in hdparm.conf. And ship with

Bug#744753: Fix for anacron (running on resume under systemd)

2015-02-27 Thread email . bug
Control: reopen 744753 Please ship a working systemd unit file as given in the last comments. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#725284:

2015-02-27 Thread email . bug
Control: reopen 725284 Udev rules are only trigged when devices appear/disapper, but not when the kernel suspends (with the device staying present and only entering a low power state) A systemd unit file is required to recover all hdparm settings that devices wrongly initialize back to factory d

Bug#707226: [pkg-wine-party] package wine does not install wine on amd64

2013-06-02 Thread email . bug
Michael, somehow I misread your response, as if you wanted me to patch other packages, but reconsidering I think you have rather expressed you'd consider a patch from me. Thanks for being willing to accept an improvement. I would certainly send a patch if I were able to. So please leave the bu

Bug#707226: [pkg-wine-party] package wine does not install wine on amd64

2013-06-02 Thread email . bug
> If you believe in that solution, please feel free to provide a patch. > Complaints without action tend to be counter-productive time wasters. Exactly. That would surely be the answer if filing this for packages that depend on wine. Exept, wine-party is resposible for a package that currently

Bug#707226: [pkg-wine-party] package wine does not install wine on amd64

2013-06-01 Thread email . bug
> No, please file a bug against the q4wine debian package about making > it more compatible with debian wine, not the upstream software. They would have to patch the application since they too can not depend on wine-bin:32. This seems to exchange the work for including a debconf question/messa

Bug#707226: [pkg-wine-party] package wine does not install wine on amd64

2013-06-01 Thread email . bug
> > Thus, the idea of letting the packet managment script provide the > message. > > Or having the front end fix their assumptions. Please consider filing > a bug against q4wine. Please sleep over this. This sounds funny to me. The debian wine package maintainers want upstream software to ada

Bug#707226: [pkg-wine-party] package wine does not install wine on amd64

2013-06-01 Thread email . bug
> Which front end are you using? It was q4wine > message should pop up via > xmessage, and if not it will be dumped to stdout. So if your front > end is preventing that, the issue should be fixed there. Unfortunately, missing files already cause errors during the frontend configuration proces

Bug#707226: package wine does not insall wine on amd64)

2013-06-01 Thread email . bug
> Are you saying that the following message was never displayed to you? Correct, the message was never displayed. As reported, I installed a frontend that depends on wine, and strange error messages popped up instead, caused by all kinds of missing files. Thus my suggestion you use a high prio

Bug#707226: package wine does not insall wine on amd64)

2013-06-01 Thread email . bug
Hello, thanks for your answer. > It is impossible for a package to install another from its postinst; > dpkg has a lock to prevent multiple simultaneous invocations, and > postinst scripts are run under the dpkg lock. Perhaps the postinst > could enable i386 multiarch, If selecting a package fo

Bug#707226: package wine does not insall wine on amd64)

2013-05-31 Thread email . bug
reopen: 707226 > If you install the wine package instead of wine-bin, you will get the > wine64-bin package, Yes, that is also what the bug title says and exaclty what happened by installing a package that depends on wine. > which will present the above helpful info to the > user. Unfortunately

Bug#707226: package wine does not insall wine on amd64

2013-05-08 Thread email . bug
Package: wine Severity: grave On a freshly installed Debian stable (wheezy) on amd64, installing a frontend like q4wine and wine seems to succeed, but running it produces strange errors. The reason: Actually, no wine binaries or libs were installed. Please add some debconf script to the wine-bin

Bug#683058: closed by Ansgar Burchardt (Re: ftp.debian.org: please create an empty wheezy-updates repository)

2012-10-10 Thread email . bug
Am Wed, 10 Oct 2012 21:09:05 + schrieb ow...@bugs.debian.org (Debian Bug Tracking System): > wheezy-updates does now exist. Thanks! Is the creation of the dir now included in the script/procedure for post wheezy releases? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org