Re: rc bugs

Hi, On Fri, 12 Sep 2014, Brian May wrote: > Lets say there is a bug in a package X, however package X is still usable > by itself. > > However package Y depends on package X, and as a result of this bug it was > an RC bug. > > Is the bug against package X also RC? A regression causing an RC bug

Re: Trimming priority:standard

> apt-listchanges aptitude aptitude-common at bash-completion bc dc bind9-host Why is aptitude still in this list? Please keep telnet. - Fabian -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Arc

Re: Trimming priority:standard

Adam Borowski writes: > What would you guys say about cutting some cruft from priority:standard? Yay. > bind9-host dnsutils host libbind9-90 libdns100 libisc95 liblwres90 Is the BIND libraries pulled in just because of 'host'? Seems rather heavy to me. Anyway, the 'host' package seems to be

Re: Trimming priority:standard

Quoting Russ Allbery (2014-09-12 04:41:19) > wamerican provides /usr/share/dict/words, which is widely used in a > variety of strange places you wouldn't expect, like random test > suites. How about the more generic (but also slightly larger) miscwords for that instead. - Jonas -- * Jonas

Re: Trimming priority:standard

Adam Borowski wrote: > What would you guys say about cutting some cruft from priority:standard? Yes please! I've been poking at this for a while, trying to reduce the number of installed-by-default packages; I've filed quite a few bugs, some of which have gotten fixed. > The current list is: >

Bug#761260: ITP: python-xstatic-bootstrap-scss -- Bootstrap-SCSS XStatic support

Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: python-xstatic-bootstrap-scss Version : 3.1.1.1 Upstream Author : Radomir Dopieralski * URL : https://github.com/stackforge/xstatic-bootstrap-scss * License : Expat Programming Lang: Pyth

Re: Trimming priority:standard

* Josh Triplett , 2014-09-12, 00:55: - gettext-base. Supports internationalized shell scripts; anything using this depends on it, and nothing in standard or above does. select-editor uses it: #728612 (I can't fathom why this tool exists in the first place.) -- Jakub Wilk -- To UNSUBSCRIBE,

Re: PackageKit cleanup: Do you use these functions?

Hi, Steve Langasek: > I understand that software (especially desktop software) not coping with > online updates is an existing problem. Not only that. What _do_ you do when version 2 of $SUPPORTING_PACKAGE implements a broken/superseded API or protocol? You limp along; you either cannot start any

Re: rc bugs

Brian May writes: > My reading of the criteria is it depends on your interpretation of "makes > unrelated software on the system break". What does "unrelated" mean? In > this case it seems they are related as package Y depends on package X. Or > maybe it means "unrelated" as in generated from dif

Re: PackageKit cleanup: Do you use these functions?

Matthias Urlichs writes: > Hi, > > Steve Langasek: >> I understand that software (especially desktop software) not coping with >> online updates is an existing problem. > > Not only that. What _do_ you do when version 2 of $SUPPORTING_PACKAGE > implements a broken/superseded API or protocol? You

ppc64 not in any-powerpc ?

I could not find the answer anywhere. Why is arch:ppc64 not in the `any-powerpc` definition ? I would have guessed arch:ppc64 to be very close to arch:powerpc... Thanks, -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas..

Re: Allow encfs into jessie?

On Thu, Sep 11, 2014 at 04:06:06PM -0400, Harlan Lieberman-Berg wrote: > On Thu, 2014-09-11 at 19:33 +0200, Eduard Bloch wrote: > > I though Jan has just described one. For example, taking a 10 year old > > CD with backups from your safe and trying to get the data back. > > Another option would be

Re: ppc64 not in any-powerpc ?

On 12/09/14 10:48, Mathieu Malaterre wrote: > I could not find the answer anywhere. Why is arch:ppc64 not in the > `any-powerpc` definition ? I would have guessed arch:ppc64 to be very > close to arch:powerpc... That would be like making any-i386 include (linux-)amd64 or (linux-)x32, which we don'

Re: ppc64 not in any-powerpc ?

On Fri, Sep 12, 2014 at 11:48:26AM +0200, Mathieu Malaterre wrote: > I could not find the answer anywhere. Why is arch:ppc64 not in the > `any-powerpc` definition ? I would have guessed arch:ppc64 to be very > close to arch:powerpc... any means "any OS", not "any arches for this hardware" https://w

Bug#761276: ITP: python-xstatic-font-awesome -- Font Awesome XStatic support

Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: python-xstatic-font-awesome Version : 4.1.0 Upstream Author : Radomir Dopieralski * URL : https://github.com/stackforge/xstatic-font-awesome * License : Expat, OFL-1.1 Programming Lang: P

Re: PackageKit cleanup: Do you use these functions?

2014-09-12 1:49 GMT+02:00 Cameron Norman : > El mié, 10 de sep 2014 a las 5:34 , Matthias Klumpp > escribió: >> [...] > > What are the options? > > I would like if apps could say somehow (maybe an extension to the AppStream > format?) whether they need offline updates, or if online is fine, so tha

Re: Allow encfs into jessie?

Hi Holger, On Thu, Sep 11, 2014 at 06:42:32PM +0200, Holger Levsen wrote: > I (probably too briefly) skimmed though the bug report, but couldn't find a > usecase where an encrypted filestem container with broken crypto could be > useful. Could you elaborate, please? As far as I understand the E

Re: PackageKit cleanup: Do you use these functions?

On Fri, Sep 12, 2014 at 01:43:01PM +0200, Matthias Klumpp wrote: [..snip..] > The problem with restarting applications and subsystems is that you > never know if the loose state information if you just restart them > (e.g. Inkscape going down on upgrade would be pretty > annoying). Also, Why shoul

Re: ppc64 not in any-powerpc ?

On Fri, Sep 12, 2014 at 12:17 PM, Andrey Rahmatullin wrote: > On Fri, Sep 12, 2014 at 11:48:26AM +0200, Mathieu Malaterre wrote: >> I could not find the answer anywhere. Why is arch:ppc64 not in the >> `any-powerpc` definition ? I would have guessed arch:ppc64 to be very >> close to arch:powerpc..

Re: Trimming priority:standard

Josh Triplett writes: > Now that libc-bin contains C.UTF-8, which we should make the default > locale, [...] It would be nice to get Debian's support for C.UTF-8 pushed to upstream glibc. At present, it's patched in by some (not all) distributions, which means that upstream authors can't rely on

Re: ppc64 not in any-powerpc ?

* Mathieu Malaterre , 2014-09-12, 14:03: I could not find the answer anywhere. Why is arch:ppc64 not in the `any-powerpc` definition ? I would have guessed arch:ppc64 to be very close to arch:powerpc... any means "any OS", not "any arches for this hardware" https://www.debian.org/doc/debian-pol

Re: Trimming priority:standard

Josh Triplett writes: > - make-guile. More of a question than a recommendation for a change, > but why is this standard and make optional, rather than the other way > around? Is this mostly about naming? GNU Make has guile-support by default, so I would say that 'make' should be with Guile

Re: upgrades must not change the installed init system

On Mon, 8 Sep 2014, Vincent Danjean wrote: > When Debian switched the default syslog implementation (to rsyslog), > upgrades did not change already installed syslog implementation. They most definitely did not do that, right. The only one which did was GRUB → GRUB 2, which required the user to i

Re: ppc64 not in any-powerpc ?

Hi, Quoting Simon McVittie (2014-09-12 12:18:35) > There might be situations where it would be useful to have a way to spell > "any member of the x86 family", "any member of the PowerPC family", "any > member of the ARM family" and "any member of the MIPS family", but we > currently don't. There

Re: systemd, again

On Mon, 8 Sep 2014, Simon McVittie wrote: > systemd is compatible with LSB (i.e. sysvinit) init scripts. So is Upstart. If LSB were == sysvinit, and not just a subset of it, we’d have had *much* less troubles at work during the forced move to insserv even with file-rc. (Spoiler: cow-orkers, espe

Re: PackageKit cleanup: Do you use these functions?

On 12/09/14 12:43, Matthias Klumpp wrote: > Now, if the user reboots, the system enters a special mode where > updates are installed using PK (progress is shown on Plymouth), then > it reboots again and enters the desktop. I've done some work on a similar feature for unattended-upgrades

Re: PackageKit cleanup: Do you use these functions?

On Thu, 11 Sep 2014, Ansgar Burchardt wrote: > Well, online updates do break software from time to time on my system. I’ve had to do unattended updates of our old Kubuntu desktop at work at shutdown time as well, due to breakage involved in upgrading them while being in use (especially the deskto

Re: Seeking help with OpenVPN scripts and systemd

On Thu, 11 Sep 2014, Gergely Nagy wrote: > OpenVPN works just fine with systemd. Its init script does not, but for Yes, but for many installations, its init script is what is required for the VPN to “work”. > There is no problem with that, at all. Right, no problem except that remote machines a

Re: PackageKit cleanup: Do you use these functions?

2014-09-12 15:35 GMT+02:00 Thorsten Glaser : > On Thu, 11 Sep 2014, Ansgar Burchardt wrote: > >> Well, online updates do break software from time to time on my system. > > I’ve had to do unattended updates of our old Kubuntu desktop at work > at shutdown time as well, due to breakage involved in up

Re: Trimming priority:standard

On Fri, 12 Sep 2014, Josh Triplett wrote: > > * dc: a RPN calculator is pretty esoteric, bc is for "normal people". > > Just filed a bug for that one. > > I'd actually argue that both bc and dc should become "optional". *no*! bc is the standard Unix calculator, normally a dc frontend, and used

Re: ppc64 not in any-powerpc ?

On Fri, 12 Sep 2014, Jakub Wilk wrote: > Because any-amd64 matches x32. (I kid you not.) > Because any-powerpc matches powerpc. powerpcspe? These are probably bugs in dpkg and related tools, and massively unexpected. On Fri, 12 Sep 2014, Simon McVittie wrote: > There might be situations whe

Re: PackageKit cleanup: Do you use these functions?

On 12/09/14 14:29, Simon McVittie wrote: > In an ideal world libraries wouldn't break > ABI either, but they do; in an ideal world libraries and applications > wouldn't have security flaws that need stable-updates, but they do. As > much as I'd like people to implement all the subtleties of re-exec

Re: Trimming priority:standard

On Thu, Sep 11, 2014 at 07:41:19PM -0700, Russ Allbery wrote: > > > * telnet: dead for 19 years. Used only by those who misspell 'nc' and hope > > for no 0xff bytes. > > * wamerican: what use is a wordlist with no users? > > Both of these fall under the "anyone familiar with UNIX would go 'whe

Bug#761289: ITP: ntpstat -- show network time protocol (ntp) status

Package: wnpp Severity: wishlist Owner: Thomas Goirand * Package name: ntpstat Version : 0.0.0.1 Upstream Author : Daniel Huckstep * URL : https://github.com/darkhelmet/ntpstat * License : GPL-2 Programming Lang: C Description : show network time proto

Re: Trimming priority:standard

On 12/09/14 14:56, Theodore Ts'o wrote: > What if we create a tasksel > task called "Unix" that installs these traditional Unix commands from > the BSD 4.x era? It would include dc, m4, /usr/dict/words, telnet, > etc. I was just about to suggest that myself. at, cron, an MTA, and locate seem good

Re: Trimming priority:standard

Le 12/09/2014 15:49, Thorsten Glaser a écrit : > On Fri, 12 Sep 2014, Josh Triplett wrote: [...] > bc is the standard Unix calculator, normally a dc frontend, > and used in *a lot* of scripts. [...] > Eh sorry? at+cron are standard Unix. [...] > But then, an MTA configured to listen and deliver loc

Re: upgrades must not change the installed init system [was: Re: Cinnamon environment now available in testing]

On Tue, 9 Sep 2014, Mathieu Parent wrote: > 4) Upgrade to systemd silently without asking the user AND add a grub > entry to use old init These are the Linux bootloaders I came up within less than five minutes of searching the ’net: • Acronis OS Selector • AiR-Boot • AKernelLoader • AMIBOOT • AP

Re: Trimming priority:standard

On Fri, 12 Sep 2014, Thibaut Paumard wrote: > I agree that all those tools belong to a standard UNIX system. However, > is that among our goals to provide people with a standard UNIX system by This is not about “by default”, but it *is* the definition of priority:standard in Debian. And yes, it’

Re: upgrades must not change the installed init system [was: Re: Cinnamon environment now available in testing]

On Tue, 9 Sep 2014, Ansgar Burchardt wrote: > We could delay the transition-on-upgrade by one release, but the > migration from sysvinit to systemd on a Jessie -> Jessie+1 upgrade will > probably end up less tested (though systemd itself would probably be > more tested by then). Nobody says jessi

Re: Trimming priority:standard

Le 12/09/2014 16:23, Thorsten Glaser a écrit : > On Fri, 12 Sep 2014, Thibaut Paumard wrote: > >> I agree that all those tools belong to a standard UNIX system. However, >> is that among our goals to provide people with a standard UNIX system by > > This is not about “by default”, but it *is* the

Re: upgrades must not change the installed init system [was: Re: Cinnamon environment now available in testing]

On Wed, 10 Sep 2014, Nick Phillips wrote: > Debian has a good and hard-earned reputation for not messing up > sysadmins' changes Agreed. This is about the only thing I can currently use to argue for use of Debian over *buntu in some places. > So, is it actually feasible to provide such a prompt?

Re: Trimming priority:standard

Simon McVittie wrote: >On 12/09/14 14:56, Theodore Ts'o wrote: >> What if we create a tasksel >> task called "Unix" that installs these traditional Unix commands from >> the BSD 4.x era? It would include dc, m4, /usr/dict/words, telnet, >> etc. > >I was just about to suggest that myself. at, cron,

Re: Trimming priority:standard

Le 12/09/2014 16:33, Thibaut Paumard a écrit : > Le 12/09/2014 16:23, Thorsten Glaser a écrit : >> On Fri, 12 Sep 2014, Thibaut Paumard wrote: >> >>> I agree that all those tools belong to a standard UNIX system. However, >>> is that among our goals to provide people with a standard UNIX system by

Re: Trimming priority:standard

On Fri, 12 Sep 2014, Thibaut Paumard wrote: > No, it's not. The actual definition is very vague and does not refer to Oh, my bad. I confused this with priority:important then. So we should probably *raise* the priority of things like bc, ed, etc. to "important". bye, //mirabilos -- 15:41⎜ Some

Re: Trimming priority:standard

Le 12/09/2014 16:37, Thorsten Glaser a écrit : > On Fri, 12 Sep 2014, Thibaut Paumard wrote: > >> No, it's not. The actual definition is very vague and does not refer to > > Oh, my bad. I confused this with priority:important then. > > So we should probably *raise* the priority of things like >

Re: Trimming priority:standard

On Fri, 12 Sep 2014, Josh Triplett wrote: * telnet: dead for 19 years. Used only by those who misspell 'nc' and hope for no 0xff bytes. A slight exaggeration. A client that uses the actual telnet protocol is still invaluable for managing various fairly stupid devices. Given the rarity of

Re: Seeking help with OpenVPN scripts and systemd

Can anyone please just read the rest of this thread before continuing this flamewar? The original question was asked, answered and the answer was deemed satisfactory. Best, Axel Wagner -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? C

Re: ppc64 not in any-powerpc ?

On Fri, Sep 12, 2014 at 03:11:08PM +0200, Johannes Schauer wrote: > The common fallacy is that the "foo" in "any-foo" is the name of a Debian > architecture while in fact it is the name of the CPU which is mapped to one or > more Debian architectures by /usr/share/dpkg/triplettable Indeed, maybe we

Re: Trimming priority:standard

On Fri, Sep 12, 2014 at 02:36:09PM +0200, Simon Josefsson wrote: > Josh Triplett writes: > > > - make-guile. More of a question than a recommendation for a change, > > but why is this standard and make optional, rather than the other way > > around? > > Is this mostly about naming? GNU Mak

Re: Trimming priority:standard

On Fri, Sep 12, 2014 at 03:12:47PM +0100, Simon McVittie wrote: > > (Admittedly, cron has to be Priority:important anyway, to support > logrotate - until/unless someone adds a logrotate.timer for systemd, and > makes its cron job early-return if systemd is pid 1.) It's inevitable that systemd wil

Re: Trimming priority:standard

* Theodore Ts'o , 2014-09-12, 13:12: It's inevitable that systemd will subsume cron, with an incompatible configuration file format. :-) I'm looking forward for systemd-mta. -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trou

Re: Trimming priority:standard

One thought... there will probably be trademark concerns with "unix".[1] So we might have to choose a name for the tasksel task to be someting like "unix-like". [1] http://www.unix.org/trademark.html - Ted -- To UNSUBSCRIBE, email to debian-devel-requ...

Re: Allow encfs into jessie?

On 09/12/2014 06:46 AM, Jan Niehusmann wrote: > A common use case for disk encryption is to protect a lost or stolen > laptop. And the adversary is not some powerful agency, but a curious > person browsing through the hard disk before formatting it. > > I see no reason to assume that encfs is not

Re: Trimming priority:standard

On 12/09/14 18:19, Theodore Ts'o wrote: > One thought... there will probably be trademark concerns with "unix".[1] > So we might have to choose a name for the tasksel task to be someting > like "unix-like". Perhaps task-traditional -- Traditional Unix utilities ? Or Un*x if you're that worri

Re: Trimming priority:standard

On Thu, 11 Sep 2014, Russ Allbery wrote: > wamerican provides /usr/share/dict/words, which is widely used in a > variety of strange places you wouldn't expect, like random test > suites. If size is an issue, I'd also be OK with migrating wamerican-small to standard (0.5M installed), and wamerican

Re: Trimming priority:standard

Theodore Ts'o wrote: > One thought... there will probably be trademark concerns with "unix".[1] > So we might have to choose a name for the tasksel task to be someting > like "unix-like". Or we could just call it "standard system". -- see shy jo signature.asc Description: Digital signature

Re: Trimming priority:standard

Theodore Ts'o wrote: > On Fri, Sep 12, 2014 at 03:12:47PM +0100, Simon McVittie wrote: > > > > (Admittedly, cron has to be Priority:important anyway, to support > > logrotate - until/unless someone adds a logrotate.timer for systemd, and > > makes its cron job early-return if systemd is pid 1.) >

Re: Trimming priority:standard

On Sep 12, 2014, at 07:18 PM, Jakub Wilk wrote: >I'm looking forward for systemd-mta. It's inevitable. ;) http://catb.org/jargon/html/Z/Zawinskis-Law.html -Barry signature.asc Description: PGP signature

Re: upgrades must not change the installed init system [was: Re: Cinnamon environment now available in testing]

On Fri, 12 Sep 2014 16:27:58 +0200, Thorsten Glaser wrote: >Nobody says jessie+1 will not permit running sysvinit any more, >and the CTTE rulings explicitly did not touch that topic which >implies some amount of scepsis. sysvinit init scripts will suffer heavy bitrot in jessie+1. Greetings Marc

Re: ppc64 not in any-powerpc ?

Hi, Quoting Andrey Rahmatullin (2014-09-12 18:14:55) > On Fri, Sep 12, 2014 at 03:11:08PM +0200, Johannes Schauer wrote: > > The common fallacy is that the "foo" in "any-foo" is the name of a Debian > > architecture while in fact it is the name of the CPU which is mapped to one > > or > > more De

Re: Allow encfs into jessie?

On 13 September 2014 02:58, John Goerzen wrote: > is ecryptfs. (LUKS and dm_crypt solve different problems.) Compared to > Do you trust ecryptfs? https://defuse.ca/audits/ecryptfs.htm says "eCryptfs appears to have a better crypto design than EncFS [4], but there are some red flags indicating

Re: Trimming priority:standard

On 09/12/2014 02:27 PM, Barry Warsaw wrote: > On Sep 12, 2014, at 07:18 PM, Jakub Wilk wrote: > >> I'm looking forward for systemd-mta. > > It's inevitable. ;) > > http://catb.org/jargon/html/Z/Zawinskis-Law.html > > -Barry Just wait for systemd-emacs. It would obsolete... all of gnuserv!

Bug#761343: ITP: piqi -- Universal schema language for JSON, XML, Protocol Buffers

Package: wnpp Severity: wishlist Owner: Matthew Maurer * Package name: piqi Version : 0.6.8 Upstream Author : Anton Lavrik * URL : http://piqi.org * License : Apache-2.0 Programming Lang: OCaml Description : Universal schema language for JSON, XML, Pro

Re: Trimming priority:standard

Hi, Huh. I have been waiting for emacs/lisp/systemd.el Manoj On September 12, 2014 7:49:45 PM PDT, John Goerzen wrote: >On 09/12/2014 02:27 PM, Barry Warsaw wrote: >> On Sep 12, 2014, at 07:18 PM, Jakub Wilk wrote: >> >>> I'm looking forward for systemd-mta. >> >> It's inevitable. ;) >>

Re: upgrades must not change the installed init system [was: Re: Cinnamon environment now available in testing]

Hi, Marc Haber: > sysvinit init scripts will suffer heavy bitrot in jessie+1. > Possibly. But let's get Jessie out the door first … -- -- Matthias Urlichs -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debia

Re: Trimming priority:standard

Hi, Edward Allcutt: > On Fri, 12 Sep 2014, Josh Triplett wrote: > >>* telnet: dead for 19 years. Used only by those who misspell 'nc' and hope > >> for no 0xff bytes. > > A slight exaggeration. A client that uses the actual telnet protocol is > still invaluable for managing various fairly stupi

Re: Seeking help with OpenVPN scripts and systemd

Hi, Thorsten Glaser: > The systemd apologetists If you want a civil dialogue with systemd proponents, please refrain from using loaded words like this one. -- -- Matthias Urlichs -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Conta