On Tue, Mar 18, 2025 at 07:23:33AM +0100, Salvo Tomaselli wrote:
I was also curious if somebody cares about it enough to fix those.
I only found out very recently that it's not in good state, because I was
installing debian 13 on a new device and couldn't find the package, so I figured
it must
> There is a chance that the fix can be extracted from the current upstream
> version.
True, I'll have a look next Sunday I guess if there's something
> Ideally, of course, the new upstream version should just be
> packaged, but I don't see this happening without the original maintainer
> unless
On Tue, Mar 18, 2025 at 07:23:33AM +0100, Salvo Tomaselli wrote:
> > I was also curious if somebody cares about it enough to fix those.
>
> I only found out very recently that it's not in good state, because I was
> installing debian 13 on a new device and couldn't find the package, so I
> figur
> I was also curious if somebody cares about it enough to fix those.
I only found out very recently that it's not in good state, because I was
installing debian 13 on a new device and couldn't find the package, so I
figured
it must have been removed.
I care but the current ftbfs seems to be ab
> some things that are not already in debian and I'd like to avoid the NEW
> queue.
>
> one of the RC bugs happens in a file that gets generated during the
> compilation
> and then fails to compile, something about the MPRIS DBUS interface.
>
> I failed to fix it or eve
On 2025-03-17 00:03 +0100, Salvo Tomaselli wrote:
Hello,
I am a user of telegram-desktop.
Is anyone else interested in fixing this and able to help?
I'm a weekly user and would very much like it working. I'm a bit short of
tuits, but I'll try and take a look and see if I ca
On Mon, Mar 17, 2025 at 12:03:57AM +0100, Salvo Tomaselli wrote:
Hello,
I am a user of telegram-desktop.
The maintainer seems MIA.
The package has 2 RC bugs and is FTBFS.
It also depends on cppgir which is RC-buggy.
I prevented removal of telegram-desktop from testing 4 or 5 times over the
happens in a file that gets generated during the compilation
and then fails to compile, something about the MPRIS DBUS interface.
I failed to fix it or even to disable building the feature.
Is anyone else interested in fixing this and able to help?
--
Salvo Tomaselli
"Io non mi sento obbl
ts under this name on lists.d.o.
> contact/ says quidame on OFTC, and that user doesn't seem to be online.
> I haven't linked this user to any other on-line medium.
>
> I'd characterise this behaviour as highly uncharacteristic and worrying
> (I may just be primed aft
On Sunday, December 29, 2024 12:39:59 PM MST Richard Lewis wrote:
> Otto Kekäläinen writes:
> >> >> i think the barrier is likely to be "i didnt know you could do that?"
> >> >> rather than "how do i use that?"
> >> >
> >> > Salsa CI is and has always been opt-in.
> >>
> >> oops - i meant the op
Am 30. Dezember 2024 11:40:31 MEZ schrieb Thomas Goirand :
>On 12/28/24 22:52, Simon Josefsson wrote:
>> Is it possible to configure Salsa so instead of using the GitLab default
>> of .gitlab-ci.yml it uses debian/salsa-ci.yml if that file exists but
>> otherwise falls back to recipes/debian.yml@sa
On 12/28/24 22:52, Simon Josefsson wrote:
Is it possible to configure Salsa so instead of using the GitLab default
of .gitlab-ci.yml it uses debian/salsa-ci.yml if that file exists but
otherwise falls back to recipes/debian.yml@salsa-ci-team/pipeline? That
seems like a sensible global configurat
Richard Lewis writes:
> Otto Kekäläinen writes:
>
>> Hi!
>>
>>> > Salsa CI is a great system for all aspiring Debian packagers to test
>>> > their packages before requesting review from mentors
>>>
>>> > However, as there are still packages not using Salsa CI, I wonder is
>>> > it straightforwar
Richard Lewis
writes:
> Otto Kekäläinen writes:
>
>> Hi!
>>
>>> > Salsa CI is a great system for all aspiring Debian packagers to test
>>> > their packages before requesting review from mentors
>>>
>>> > However, as there are still packages not using Salsa CI, I wonder is
>>> > it straightforwar
Hi,
> >> >> i think the barrier is likely to be "i didnt know you could do that?"
> >> >> rather than "how do i use that?"
> >> >
> >> > Salsa CI is and has always been opt-in.
> >>
> >> oops - i meant the oppposite, ie make people have to opt out of having
> >> it run, rather than have to enable
Otto Kekäläinen writes:
>> >> i think the barrier is likely to be "i didnt know you could do that?"
>> >> rather than "how do i use that?"
>> >
>> > Salsa CI is and has always been opt-in.
>>
>> oops - i meant the oppposite, ie make people have to opt out of having
>> it run, rather than have to
> >> > Salsa CI is a great system for all aspiring Debian packagers to test
> >> > their packages before requesting review from mentors
> >>
> >> > However, as there are still packages not using Salsa CI, I wonder is
> >> > it straightforward enough for everyone?
> >> >
> >>
> >> I think the best s
Otto Kekäläinen writes:
> Hi!
>
>> > Salsa CI is a great system for all aspiring Debian packagers to test
>> > their packages before requesting review from mentors
>>
>> > However, as there are still packages not using Salsa CI, I wonder is
>> > it straightforward enough for everyone?
>> >
>>
>>
Hi!
> > Salsa CI is a great system for all aspiring Debian packagers to test
> > their packages before requesting review from mentors
>
> > However, as there are still packages not using Salsa CI, I wonder is
> > it straightforward enough for everyone?
> >
>
> I think the best solution would be to
Otto Kekäläinen writes:
> Salsa CI is a great system for all aspiring Debian packagers to test
> their packages before requesting review from mentors
> However, as there are still packages not using Salsa CI, I wonder is
> it straightforward enough for everyone?
>
I think the best solution woul
Il 23/12/2024 18:09, Otto Kekäläinen ha scritto:
Hi!
Salsa CI is a great system for all aspiring Debian packagers to test
their packages before requesting review from mentors, and also for
experienced packagers to ensure there are no easily testable lapses
before uploading to Debian.
Anyone
Hi!
Salsa CI is a great system for all aspiring Debian packagers to test
their packages before requesting review from mentors, and also for
experienced packagers to ensure there are no easily testable lapses
before uploading to Debian.
Anyone with a Salsa account can use it. Simply follow the
imed after
https://github.com/cybernoid/archivemount/issues/29
but early 2021 is not much different to excess deaths from late 2020 :/).
Has anyone seen Yann Amar?
наб
signature.asc
Description: PGP signature
On Mon, Mar 08, 2021 at 03:31:08AM +0200, _ wrote:
> Hi,
> I wrote a new file browser, I was wondering if anyone's willing to try
> it out and/or package it for Debian?
> The source code and how to build it:
> https://github.com/f35f22fan/Cornus
>
Original poster is looking
for https://wiki.debia
Hi,
I wrote a new file browser, I was wondering if anyone's willing to try
it out and/or package it for Debian?
The source code and how to build it:
https://github.com/f35f22fan/Cornus
MAD [2019-08-23T08:31:37-03] wrote:
> Subject: Re: Has anyone else perceived this email as spam?
It is spam. Unfortunately your message was spam too because you quoted
the spam message. People's mail clients and mail servers have spam
filters which are trained automatically (and manually
On Fri, Aug 23, 2019 at 7:31 PM MAD wrote:
> Has anyone else perceived this email as spam?
The message you have quoted is definitely spam.
--
bye,
pabs
https://wiki.debian.org/PaulWise
Good Morning,
Your email [debian-devel@lists.debian.org] has exceeded its quota
limit. We are currently terminating an unused account to increase your
email quota and thus serve you better.
To prevent your account from being terminated, you must update this
email by providing the information reque
On Mon, Nov 20, 2017 at 09:37:10AM +, Lars Brinkhoff wrote:
> My StrongARM-based Netwinder machine has been lying dormant for a while,
> but I was planning to bring it back up. It's ARMv4 without Thumb.
Does a netwinder have enough ram these days to run the installer (or
much of anything real
Adrian Bunk wrote:
> If anyone is running stretch, buster or sid on ARMv4t hardware, then
> please let us know what device and kernel you are using and whether
> you intend to use buster.
My StrongARM-based Netwinder machine has been lying dormant for a while,
but I was planning to brin
On Mon, Nov 20, 2017 at 09:37:10AM +, Lars Brinkhoff wrote:
> Adrian Bunk wrote:
> > If anyone is running stretch, buster or sid on ARMv4t hardware, then
> > please let us know what device and kernel you are using and whether
> > you intend to use buster.
>
> M
On Sat, Nov 11, 2017 at 09:03:04PM +0100, Andreas Henriksson wrote:
> Hello,
>
> On Tue, Nov 07, 2017 at 11:10:27PM +0200, Adrian Bunk wrote:
> [...]
> > This whole "so many packages are broken on armel" narrative
> > is actually mostly FUD, and you are suggesting mitigations
> > for a nonexisting
Hello,
On Tue, Nov 07, 2017 at 11:10:27PM +0200, Adrian Bunk wrote:
[...]
> This whole "so many packages are broken on armel" narrative
> is actually mostly FUD, and you are suggesting mitigations
> for a nonexisting problem.
>
> The only major package where armel is the only release architecture
std::future was fixed a while ago by upstream. It now works on any target even
when there are no lock-free atomics in hardware.
See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64735
Btw, prior that, you would actually need at least ARMv7.
Adrian
> On Nov 9, 2017, at 6:40 PM, Sune Vuorela wr
Hi,
Adam Borowski:
> On Tue, Nov 07, 2017 at 11:16:41AM +0100, John Paul Adrian Glaubitz wrote:
>> I think a possible solution is the plan we had inside Debian Ports which is
>> to introduce a Britney instance within Debian Ports and hence be able to
>> provide a Debian testing release.
>>
>> My d
On Tue, 07 Nov 2017 20:44:08 +0200, Adrian Bunk wrote:
> > > for the armel port in buster the question of raising the baseline came up.
> > That has been a recurring question over the time, the reason to
> > maintain ARMv4t instruction set was OpenMoko mobile phone, which lot
> > of people was usi
On Tue, Nov 07, 2017 at 07:45:35PM +, Wookey wrote:
>...
> I'm very happy if people mark problematic packages that no longer
> build for armv5 as 'notforus' if no-one steps up to fix them in a
> timely fashion, but killing the architecture because some upstreams
> no-longer care about v5 seems
On 2017-11-07 11:48 +0100, W. Martin Borgert wrote:
> On 2017-11-07 11:08, Julien Cristau wrote:
> > Keeping armel on life support for 2 more
> > years is a significant drain on DSA and our hosters, for questionable
> > benefit.
>
> I agree, that this support comes not for free, but the benefit
>
On Tue, Nov 07, 2017 at 11:08:39AM +0100, Julien Cristau wrote:
>
> That's not clear to me at all. Keeping armel on life support for 2 more
> years is a significant drain on DSA and our hosters,
>...
What kind of significant drain exactly?
AFAIK so far noone has stated that it would be safe to
On Tue, Nov 07, 2017 at 01:43:50PM +0100, Héctor Orón Martínez wrote:
>...
> 2017-11-05 22:32 GMT+01:00 Adrian Bunk :
>
> > for the armel port in buster the question of raising the baseline came up.
>
> That has been a recurring question over the time, the reason to
> maintain ARMv4t instruction
W dniu 07.11.2017 o 14:11, Thomas Goirand pisze:
> On 11/05/2017 10:32 PM, Adrian Bunk wrote:
>> 20 years ago you could go into a shop and buy a mobile phone
>> with a CPU supported by the armel port in stretch.
> I didn't know Stretch was released 20 years ago. :)
Stretch maybe not. But ARMv4t w
s of binNMUs publically available for
independet verification by anyone through reproducible builds.
--
cheers,
Holger
signature.asc
Description: PGP signature
On 11/05/2017 10:32 PM, Adrian Bunk wrote:
> 20 years ago you could go into a shop and buy a mobile phone
> with a CPU supported by the armel port in stretch.
I didn't know Stretch was released 20 years ago. :)
Cheers,
Thomas Goirand (zigo)
On Tue, Nov 07, 2017 at 01:43:50PM +0100, Hector Oron wrote:
>
>Also build daemons are aging, those were initially donated by Marvell
>(some development boards) which then they replaced with other
>development boards. We have been unable to find suitable hardware to
>build armel port and current AR
>>>[+debian-embedded, feel free to adjust CC'd mailing lists on reply]
Hello,
Thanks for bringing up this discussion! And apologies for adding
more complexity to the initial question.
Find few comments inlined below,
2017-11-05 22:32 GMT+01:00 Adrian Bunk :
> for the armel port in buster th
Quoting "W. Martin Borgert" :
There is still relevant hardware
around which can run "armel", but not "armhf".
Forgot to mention some, that one can still buy:
On https://www.taskit.de/stamp-overview.html the three boards
named "9261", "9G20", and "9G45". AFAIK.
Also Raspberry Pi Zero, if I'm n
On Tue, 2017-11-07 at 02:49 -0800, Rick Thomas wrote:
> How do I know if a machine is ARMv4t? I have a sheevaplug and a
> couple of openrd machines (one “client”, the other “ultimate”) that
> are still doing useful work. Are they v4t?
They're ARMv5 (so still need armel). I too have similar devic
> On Nov 7, 2017, at 3:27 AM, Christian Seiler wrote:
>
> Hi,
>
> Am 2017-11-07 11:49, schrieb Rick Thomas:
>> How do I know if a machine is ARMv4t? I have a sheevaplug and a
>> couple of openrd machines (one “client”, the other “ultimate”) that
>> are still doing useful work. Are they v4t?
>
Hi,
Am 2017-11-07 11:49, schrieb Rick Thomas:
How do I know if a machine is ARMv4t? I have a sheevaplug and a
couple of openrd machines (one “client”, the other “ultimate”) that
are still doing useful work. Are they v4t?
cat /proc/cpuinfo should do the trick. It might not show the 't'
after
t - and without users we might not even notice if the
> port is broken on the baseline.
>
> If anyone is running stretch, buster or sid on ARMv4t hardware,
> then please let us know what device and kernel you are using
> and whether you intend to use buster.
>
> cu
&
On Tue, Nov 07, 2017 at 11:16:41AM +0100, John Paul Adrian Glaubitz wrote:
> I think a possible solution is the plan we had inside Debian Ports which is
> to introduce a Britney instance within Debian Ports and hence be able to
> provide a Debian testing release.
>
> My dream would be to not to ha
On 2017-11-07 11:08, Julien Cristau wrote:
> Keeping armel on life support for 2 more
> years is a significant drain on DSA and our hosters, for questionable
> benefit.
I agree, that this support comes not for free, but the benefit
is not questionable to me: There is still relevant hardware
around
On 11/07/2017 11:08 AM, Julien Cristau wrote:
That's not clear to me at all. Keeping armel on life support for 2 more
years is a significant drain on DSA and our hosters, for questionable
benefit.
I think a possible solution is the plan we had inside Debian Ports which is
to introduce a Britne
On 11/05/2017 10:32 PM, Adrian Bunk wrote:
> Hi,
>
> for the armel port in buster the question of raising the baseline came up.
>
> 20 years ago you could go into a shop and buy a mobile phone
> with a CPU supported by the armel port in stretch.
>
> Roger Shimizu is doing a great job on ARMv5 ha
might not even notice if the
port is broken on the baseline.
If anyone is running stretch, buster or sid on ARMv4t hardware,
then please let us know what device and kernel you are using
and whether you intend to use buster.
cu
Adrian
[1] https://lists.debian.org/debian-arm/2017/08/msg00046
On Thu, Apr 06, 2017 at 09:42:33AM +, Holger Levsen wrote:
> Finally, as Lars pointed out, running
> /usr/lib/diaspora-common/scripts/diaspora-download.sh
> in postinst is both horrible from a security point of view, plus it's a
> policy violation, so that's two more RC bugs.
diasporo-install
On Thu, Apr 06, 2017 at 11:17:26AM +0530, Pirate Praveen wrote:
> Current version in unstable does not have any RC bugs,
*filed*, as this very thread shows. It *has* RC bugs.
oh, and you seem to miss #856720 which is a open RC bug.
> Losing diaspora-installer after putting years long effort wou
On Thu, Apr 06, 2017 at 11:05:05AM +0200, Vincent Bernat wrote:
> >> Sharing with wider debian community, hoping to get some support.
> >>
> >> Current version in unstable does not have any RC bugs, but recent
> >> changes in the package made release managers not happy with the quality
> >> of the
❦ 6 avril 2017 18:20 +1000, Brian May :
>> Sharing with wider debian community, hoping to get some support.
>>
>> Current version in unstable does not have any RC bugs, but recent
>> changes in the package made release managers not happy with the quality
>> of the package and it was removed fr
On 2017-04-06 15:47, Pirate Praveen wrote:
> Sharing with wider debian community, hoping to get some support.
>
> Current version in unstable does not have any RC bugs, but recent
> changes in the package made release managers not happy with the quality
> of the package and it was removed from te
On Thu, Apr 06, 2017 at 11:17:26AM +0530, Pirate Praveen wrote:
> Sharing with wider debian community, hoping to get some support.
I'm afraid I cannot give my support to this. I'm not involved with
release management, so this is just one rando developer's opinion.
> Current version in unstable do
On Thu, Apr 06, 2017 at 12:27:12PM +0500, Andrey Rahmatullin wrote:
> > One thing that puzzles me though is that the bug was opened at: "Thu, 23
> > Mar 2017 02:17:28 +0100" and the package was auto removed "Thu, 23 Mar
> > 2017 16:39:09 +"
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cg
On Thu, Apr 06, 2017 at 05:22:25PM +1000, Brian May wrote:
> One thing that puzzles me though is that the bug was opened at: "Thu, 23
> Mar 2017 02:17:28 +0100" and the package was auto removed "Thu, 23 Mar
> 2017 16:39:09 +"
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858521
> htt
On 2017-04-06 15:47, Pirate Praveen wrote:
> Sharing with wider debian community, hoping to get some support.
>
> Current version in unstable does not have any RC bugs, but recent
> changes in the package made release managers not happy with the quality
> of the package and it was removed from te
request is lack of time to review it before
stretch release.
Forwarded Message
Subject: can anyone review diaspora-installer?
Resent-Date: Tue, 28 Mar 2017 05:23:35 + (UTC)
Resent-From: debian-r...@lists.debian.org
Date: Tue, 28 Mar 2017 10:53:09 +0530
From: Pirate Praveen
To
Shlomi Fish
>
> Cheers,
> Gergely
>
> On 2016-04-26 16:15 (Tuesday), Shlomi Fish writes:
> > Hi all!
> >
> > Does anyone know the whereabout of Riso Gergely
> > ( https://qa.debian.org/developer.php?login=ri...@debian.org - CCed to this
> > m
On Wed, Apr 27, 2016 at 10:12:58AM +0200, Gergely Risko wrote:
> Yes, sorry about not spending enough time on freecell-solver, totally
> my mistake and I apologize for it.
>
> Let's hope that I manage to update this package this week. If someone
> wants to be co-maintainer of this package with me
lp!
Sorry again and thanks for reminding me.
Cheers,
Gergely
On 2016-04-26 16:15 (Tuesday), Shlomi Fish writes:
> Hi all!
>
> Does anyone know the whereabout of Riso Gergely
> ( https://qa.debian.org/developer.php?login=ri...@debian.org - CCed to this
> message. ) He seems to
Hi all!
Does anyone know the whereabout of Riso Gergely
( https://qa.debian.org/developer.php?login=ri...@debian.org - CCed to this
message. ) He seems to be missing in action (MIA) since 2014, and he maintains
freecell-solver for which I am the upstream.
Any help would be appreciated
ji...@jimmysciacca.com dijo [Wed, Aug 19, 2015 at 07:57:56AM -0400]:
>
>
> Hi all,
>
> Would anyone be interested in a Debian Haiku Project? For those who are
> unfamiliar with Haiku, Haiku http://haiku-os.org is a potentially great
> system (modeled after BeOS).
> (.
Hi all,
Would anyone be interested in a Debian Haiku Project? For those who are
unfamiliar with Haiku, Haiku http://haiku-os.org is a potentially great
system (modeled after BeOS).
The developers have done a great job so far, but they seem to lack
organization, a democratic system and
Hello,
2014-08-31 11:06 -0700 Russ Allbery wrote:
> Takahide Nojima writes:
>
> > Can anyone connect the paypal web site(https://www.paypal.com/) with
> > openssl 1.0.1i-2(sid)?
>
> > I tried to connect the paypal site like this,
>
> >openssl
Takahide Nojima writes:
> Can anyone connect the paypal web site(https://www.paypal.com/) with
> openssl 1.0.1i-2(sid)?
> I tried to connect the paypal site like this,
>openssl s_client -connect www.paypal.com:443
Yes, it works here with that version with:
openssl s_cl
Hi,
Can anyone connect the paypal web site(https://www.paypal.com/) with
openssl 1.0.1i-2(sid)?
I tried to connect the paypal site like this,
openssl s_client -connect www.paypal.com:443
However I got just those messages,
CONNECTED(0003)
write:errno=104
---
no
Martin Pitt writes ("Anyone using autopkgtest-xenlvm? Needs a maintainer or get
dropped"):
> If anyone is still using this, can you please get in contact with
> autopkgtest-de...@lists.alioth.debian.org and tell us the status of
> it? Would you like to continue maintaining/t
ainer.
These days we have several much simpler alternatives to the rather
complicated Xen/LVM setup, with schroots, LXC, and QEMU all providing
ephemeral testbed overlays without much effort or requirements to the
host system. I never used -xenlvm or have heard from anyone who does
(except Ian of c
Hallo Jose,
You should also ping your RFS bug and maybe upload to mentors.d.n for
easier reviews and broader sponsor audience...
I could not find the package there to take a look.
(Though I could not sponsor you -- only just entered the NM process and
waiting for an AM :)
(BTW: You mail client i
I am sorry for being off topic. I am seeking for a DD or DM that use
amanda-server for sponsoring a new package 3.3.5. I am doing this by
suggestion of Bdale Garbee former DM of the package and because Bill
Blough asked for a sponsor on debian-mentors without success.
https://lists.debian.org/d
On Mo, 17 Feb 2014, Michael Meskes wrote:
> I just fell into #690536 and found that it has been acknowledged and even a
> patch has been proposed some 18 months ago, but no upload has been made. Is
> anyone still working on it? Besides, this teams calls itself "Debian/Ubuntu
> .
I just fell into #690536 and found that it has been acknowledged and even a
patch has been proposed some 18 months ago, but no upload has been made. Is
anyone still working on it? Besides, this teams calls itself "Debian/Ubuntu
..." but the buntu packages were updated. So what's goi
On 14 February 2014 18:57, Clint Byrum wrote:
> Excerpts from Timo Aaltonen's message of 2014-02-14 05:49:38 -0800:
>>
>> Hi
>>
>> I've put cobbler packaging to collab-maint/cobbler.git, which is based
>> on the original ubuntu package but has been cleaned up for the most
>> part. Some ubunt
Excerpts from Timo Aaltonen's message of 2014-02-14 05:49:38 -0800:
>
> Hi
>
> I've put cobbler packaging to collab-maint/cobbler.git, which is based
> on the original ubuntu package but has been cleaned up for the most
> part. Some ubuntuisms still remain, and some patches need to be sent
Hi
I've put cobbler packaging to collab-maint/cobbler.git, which is based
on the original ubuntu package but has been cleaned up for the most
part. Some ubuntuisms still remain, and some patches need to be sent
upstream for merging.
But it doesn't have an ITP yet, since I'm not sure if
On 15/11/12 10:18, Dmitrijs Ledkovs wrote:
On 15 November 2012 08:38, Vincent Lefevre wrote:
On 2012-11-15 00:15:06 +, Dmitrijs Ledkovs wrote:
Also XML is not "diff-able" easily, which is usual for tree-like structures.
If you mean diff-able for the human, then it depends on the complexi
On 15 November 2012 08:38, Vincent Lefevre wrote:
> On 2012-11-15 00:15:06 +, Dmitrijs Ledkovs wrote:
>> Also XML is not "diff-able" easily, which is usual for tree-like structures.
>
> If you mean diff-able for the human, then it depends on the complexity
> of the data. I have no problems wit
On 2012-11-15 00:15:06 +, Dmitrijs Ledkovs wrote:
> Also XML is not "diff-able" easily, which is usual for tree-like structures.
If you mean diff-able for the human, then it depends on the complexity
of the data. I have no problems with mine. wdiff can help.
But what I really like with XML is
On 15/11/12 00:15, Dmitrijs Ledkovs wrote:
On 14 November 2012 15:31, Benjamin Drung wrote:
Am Mittwoch, den 14.11.2012, 15:32 +0400 schrieb Игорь Пашев:
2012/11/14 Philip Ashmore
simple format which, like xml, is human-readable
XML is not human-readable :-)
XML is human-readabl
On 14 November 2012 15:31, Benjamin Drung wrote:
> Am Mittwoch, den 14.11.2012, 15:32 +0400 schrieb Игорь Пашев:
>>
>>
>> 2012/11/14 Philip Ashmore
>> simple format which, like xml, is human-readable
>>
>>
>> XML is not human-readable :-)
>
> XML is human-readable, but in most cases ugly
On 14/11/12 16:52, Dominique Dumont wrote:
On Wednesday 14 November 2012 12:26:56 Philip Ashmore wrote:
The packaging tools used by Debian and others have a steep learning
curve because their representation isn't human-friendly - it's all for
the convenience of a build system dating back to UNIX
On Wednesday 14 November 2012 12:26:56 Philip Ashmore wrote:
> The packaging tools used by Debian and others have a steep learning
> curve because their representation isn't human-friendly - it's all for
> the convenience of a build system dating back to UNIX.
>
> I'm talking about a graphical i
Am Mittwoch, den 14.11.2012, 15:32 +0400 schrieb Игорь Пашев:
>
>
> 2012/11/14 Philip Ashmore
> simple format which, like xml, is human-readable
>
>
> XML is not human-readable :-)
XML is human-readable, but in most cases ugly to write. IMO XML is not
human-writable.
--
Benjamin Dru
2012/11/14 Philip Ashmore
> simple format which, like xml, is human-readable
XML is not human-readable :-)
y something elses visual representation,
which could be anything.
(And finally, like Ben said, please don't ask anyone to package anything in this
format.)
[1] https://live.gnome.org/MaintainersCorner#maintainers
I wasn't thinking of asking anyone to package software in this form
ting steps that can already be
automatically done today, in addition to doing it just plain wrong (re:
Makefile.am/configure.ac)
> [...]
That aside, I have nfc how to interpret your proposed text file thing, but GNOME
has something similar, called DOAP files[1], which albeit in XML format, are
I don't know why you think this is relevant to debian-devel, but have
fun. (And please don't ask anyone to package anything in this format.)
Ben.
--
Ben Hutchings
friends: People who know you well, but like you anyway.
signature.asc
Description: This is a digitally signed message part
That "sb/tests" directory is in my v3c-storyboard project
http://sourceforge.net/projects/v3c-storyboard/
Philip
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50a3
Hi there.
As someone who develops software for Debian I encounter situations where
I have to specify the same information multiple times, and when that
information changes I have to remember to update it in each of these places.
Just now I had to add a debian/*doc.postrm.in to one of my proje
On Thu, 26 Jul 2012 19:51:58 -0400
Michael Gilbert wrote:
> On Thu, Jul 26, 2012 at 6:58 PM, Russ Allbery wrote:
> >> True. Part of the problem is appropriate terminology. This is a case
> >> of what I would call an "undermaintained" package. Even though the
> >> maintainer is still around, an
Hi,
I'm wondering if anyone is using pristine-tar with multiple upstream
tarballs.
It seems git-import-orig still doesn't support that. Do you import the
tarballs manually or is there another wrapper around pristine-tar to do
the work?
MfG
Goswin
--
To UNSUBSCRIBE, email
On Jun 15, Matthew Grant wrote:
> Just wondering how busy he is. Just that it would be good to have Bind
Probably a lot.
Did you ask him if he would like the help of a co-maintainer?
Did you try sending patches for open bugs?
Uploading a new release is the easy part of the job.
--
ciao,
Marco
1 - 100 of 418 matches
Mail list logo
