Re: Version numbering for security uploads of native packages

[Reinhard Tartler]

Gunnar Wolf <[EMAIL PROTECTED]> writes:

> At some point in 2006, a serious flaw is addressed via a NMU, so
> it sits at 1.0+sarge1. I still cannot be bothered to take a look at
> the damn package. Time passes. In March 2008 it (again) shows it needs
> to be taken care of, and you kindly prepare a new NMU, properly
> labeling it 1.0+etch1.
>
> It gets rejected, as it is a lower version.

how about having it uploaded as 1.0+sarge1+etch1. looks funny, but
actually follows the policy that says to 'append' +etch1 to such uploads.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4


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

Re: Debian refpolicy and core SELinux package update

[Raphael Hertzog]

Hi,

On Wed, 19 Mar 2008, Manoj Srivastava wrote:
> I am beginning to come back from a deadline crunch on my day
>  job, and start paying attention to my Debian packages again; so
>  hopefully the state of SELinux in Debian will improve -- at least, I'll
>  try to be more reactive in the future.
> 
> anyway, kick the tyres, look at the Debian diffs with regards to
>  the upstream refpolicy.  We should have a dialog about which changes
>  need to be purged, and which should be fed upstream.

FYI, it looks like some folks at Tresys did work on SELinux support in
Ubuntu hardy (their next "long term support" release). You thus might want
to check out the Ubuntu diff (assuming upstream packages are in sync) for
possible improvements.

http://www.outflux.net/blog/archives/2008/03/16/selinux-in-hardy/

Ideally, you might also convince the Tresys people to work directly on
Debian so that both Ubuntu and Debian benefit from their work. :-)

Regards,
-- 
Raphaël Hertzog

Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/


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

Re: source:Version and ancient dpkg-dev

[Oohara Yuuma]

On Wed, 19 Mar 2008 08:36:39 +0100,
Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> On Tue, 18 Mar 2008, Oohara Yuuma wrote:
> > According to the changelog, substvars source:Version is added in
> > dpkg-dev 1.13.19.  A package which uses source:Version in its
> > debian/control and doesn't set its value explicitly can't be built
> > with ancient dpkg-dev. The problem is that dpkg-dev in the
> > build-essential list is dpkg-dev (>= 1.13.5), which is not new enough.
> > I think the build-essential list should be updated.
> 
> This is not needed:
> - updating build-essential would update it for lenny/sid only
> - only oldstable (sarge) has a dpkg version that doesn't support it
> 
> Thus fixing build-essential doesn't fix it for the only case where it's
> broken, when building on sarge.
> 
Fixing build-essential does fix it at least for my case; my machine
was partially-upgraded sarge.  Is versioned dependency for preventing
such stupidity?

-- 
Oohara Yuuma <[EMAIL PROTECTED]>

If we know when, can we do it right?
--- TAITO "Ray Crisis"


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

Re: source:Version and ancient dpkg-dev

[Paul Wise]

On Thu, Mar 20, 2008 at 6:41 PM, Oohara Yuuma <[EMAIL PROTECTED]> wrote:

>  Fixing build-essential does fix it at least for my case; my machine
>  was partially-upgraded sarge.  Is versioned dependency for preventing
>  such stupidity?

I'm curious why you are using sarge? Any particular reason or just intertia?

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


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

Re: source:Version and ancient dpkg-dev

[Raphael Hertzog]

On Thu, 20 Mar 2008, Oohara Yuuma wrote:
> > This is not needed:
> > - updating build-essential would update it for lenny/sid only
> > - only oldstable (sarge) has a dpkg version that doesn't support it
> > 
> > Thus fixing build-essential doesn't fix it for the only case where it's
> > broken, when building on sarge.
>
> Fixing build-essential does fix it at least for my case; my machine
> was partially-upgraded sarge.  Is versioned dependency for preventing
> such stupidity?

Versioned dependency from what on what?

I doubt you have a build-essential coming from lenny/sid on your sarge
machine. In all other cases, we come back to my previous explanation.

We do our best to support partial upgrades, but supporting compilation
of (testing/unstable) packages on machines which are running a partially
upgraded olstable is not something we target.

Ideally the package maintainer has added a versioned build-dependency on
the dpkg-dev when he started using ${source:Version} but we typically tend
to drop such versioned dependencies when they concern oldstable only.

Cheers,
-- 
Raphaël Hertzog

Le best-seller français mis à jour pour Debian Etch :
http://www.ouaza.com/livre/admin-debian/


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

Bug#471834: proposition to split /etc/network/interfaces

[Bartosz Fenski aka fEnIo]

Package: netbase
Version: 4.29
Severity: wishlist

I would like to RFC about splitting /etc/network/interfaces to several
files ie. one file for each interface.

Something like /etc/network/interfaces.d/ with files eth0, wlan0, ppp0,
etc.

That would make easier to maintain machines with several (or even hundreds)
of interfaces which is quite common in big environments.

I doubt it's good goal for lenny release, but maybe it would be possible to
make it happen between lenny+1?

Any comments on that?

regards
fEnIo

-- 
  ,''`.  Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | irc:fEnIo
 : :' :   32-050 Skawina - Glowackiego 3/15 - malopolskie v. - Poland
 `. `'   phone:+48602383548 | proud Debian maintainer and user
   `-http://fenski.pl | xmpp:[EMAIL PROTECTED] | rlu:172001


signature.asc
Description: Digital signature

Re: Installation of suggested packages: recursive or not?

[Daniel Burrows]

On Thu, Mar 20, 2008 at 12:38:17PM +0900, Charles Plessy <[EMAIL PROTECTED]> 
was heard to say:
> Le Wed, Mar 19, 2008 at 02:05:05PM -0400, Joe Smith a écrit :
> > >On Wed, 19 Mar 2008, Don Armstrong wrote:
> > >>
> > >>apt-get -o APT::Install-Suggests=true install foo; or similar.
>  
> > I will say the following. I fully agree that "--install-suggests" should 
> > exist, and should do the right thing.
> 
> Hi all,
> 
> I was about to submit a wishlist bug, and then wondererd: isn't '-o
> APT::Install-Suggests=true' recursive? (In the sense that it will also
> add the suggested packages from the suggested packages.) The
> --install-suggests I have in my mind is not: the user cases would be
> with our CDD metapackages, that either Recommend or Suggest, or packages
> like t-coffee or bioperl that have a long list of suggested packages
> that are usually dispensable.

  Yes, it is.  That's why I yanked it from aptitude: at the time,
turning on the installation of Suggests would reliably result in huge
swathes of packages being installed for some innocuous program.  This
may have changed since then.

  To see (more or less) what installing Suggests will do to your system,
run:

aptitude -s -o 'APT::Install-Suggests=true' -o 
'APT::AutoRemove::SuggestsImportant=true' install '~RBsuggests:~i'

  On my computer, after a pile of dependency failures, I got:

0 packages upgraded, 386 newly installed, 1 to remove and 2 not upgraded.
Need to get 505MB of archives. After unpacking 1854MB will be used.

  Some people will find that acceptable, others won't.


  A secondary problem is that automatic dependency removal will remove
packages whose strongest link to a manual package is a Suggests.  If you
ever turn on Suggests-installation as a one-shot deal, you need to
either also mark all the suggested packages as manual, or turn on "keep
suggested packages on the system" (APT::AutoRemove::Suggests-Important).


  BTW, aptitude already supports non-recursively installing Suggests, and
flagging them as manual at the same time: "~Rsuggests:^package$" will
install everything that's directly suggested by "package".

  Daniel


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

Re: BitTorrent and ISP interference

[Clint Adams]

On Thu, Mar 20, 2008 at 08:50:11AM +1100, Ben Finney wrote:
> William, please follow the Debian mailing list code of conduct
> http://www.debian.org/MailingLists/#codeofconduct>; specifically,
> don't send me individual messages that are also sent to the list,
> since I didn't ask for them.

How many times do people have to cite this stupid thing before someone
removes it from the website?


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

Bug#471846: ITP: josm-plugins -- Plugins for JOSM (Java OpenStreetMap editor)

[Giovanni Mascellani]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, [EMAIL PROTECTED]


   Package name: josm-plugins
Version: undefined, all plugins have independent version numbers
Upstream Author: many authors, check them of URL below
URL: http://josm.openstreetmap.de/wiki/Plugins
License: GPL for most of the plugins, but I'll check it more
 carefully
Description: Plugins for JOSM (Java OpenStreetMap editor)
 JOSM (Java OpenStreetMap) plugin collection.
 .
 JOSM is an editor for OpenStreetMap (OSM) written in Java.
 The current version supports stand alone GPX tracks, GPX track data
 from OSM database and existing nodes, line segments and metadata tags
 from the OSM database.
 .
 OpenStreetMap is a project aimed squarely at creating and providing
 free geographic data such as street maps to anyone who wants them. 
 The project was started because most maps you think of as free actually
 have legal or technical restrictions on their use, holding back people
 from using them in creative, productive or unexpected ways.

This package will be maintained under the pkg-grass umbrella.

Regards, Giovanni.
-- 
Giovanni Mascellani <[EMAIL PROTECTED]>
Pisa, Italy

Web: http://giomasce.altervista.org
SIP: [EMAIL PROTECTED]
Jabber: [EMAIL PROTECTED] / [EMAIL PROTECTED]
GPG: 0x5F1FBF70 (FP: 1EB6 3D43 E201 4DDF 67BD  003F FCB0 BB5C 5F1F BF70)



signature.asc
Description: PGP signature

Re: BitTorrent and ISP interference

[brian m. carlson]

[Ignoring the part of M-F-T that indicates Ben Finney, per his request.]

On Thu, Mar 20, 2008 at 11:31:22AM -0400, Clint Adams wrote:

On Thu, Mar 20, 2008 at 08:50:11AM +1100, Ben Finney wrote:

William, please follow the Debian mailing list code of conduct
http://www.debian.org/MailingLists/#codeofconduct>; specifically,
don't send me individual messages that are also sent to the list,
since I didn't ask for them.


How many times do people have to cite this stupid thing before someone
removes it from the website?


I think it's a good idea.  I'm not a DD, but I don't appreciate getting 
dupe messages from the list.  procmail is not set up to handle them, and 
I read the vast majority of the lists I post to.  I only wish non-Debian 
lists had the same policy.


Ignoring that particular provision, it contains useful tips such as
only post in English (on non-localized lists), use the proper list, and 
don't send HTML email.  These are all things I think we should encourage 
on Debian lists, and on lists in general.


--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only
troff on top of XML: http://crustytoothpaste.ath.cx/~bmc/code/thwack
OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187


signature.asc
Description: Digital signature

I've visited your website http://lists.debian.org/debian-user-icelandic/2006/09/msg00011.html

[info]

Hi,

We've seen your website at 
http://lists.debian.org/debian-user-icelandic/2006/09/msg00011.html 
and we love it!

We see that your traffic rank is 5193 
and your link popularity is 1845. 
Also, you have been online since 3/10/1999. 

With that kind of traffic, we will pay you up to $4,800/month 
to advertise our links on your website.

If you're interested, read our terms from this page:
http://www.contactthem.ws/hit.php?s=10&p=2&w=104534

Sincerely,

patricia hong
The ContactThem Network




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

Re: Debian refpolicy and core SELinux package update

[Manoj Srivastava]

On Thu, 20 Mar 2008 09:34:38 +0100, Raphael Hertzog <[EMAIL PROTECTED]> said: 

> Hi,
> On Wed, 19 Mar 2008, Manoj Srivastava wrote:
>> I am beginning to come back from a deadline crunch on my day job, and
>> start paying attention to my Debian packages again; so hopefully the
>> state of SELinux in Debian will improve -- at least, I'll try to be
>> more reactive in the future.
>> 
>> anyway, kick the tyres, look at the Debian diffs with regards to the
>> upstream refpolicy.  We should have a dialog about which changes need
>> to be purged, and which should be fed upstream.

> FYI, it looks like some folks at Tresys did work on SELinux support in
> Ubuntu hardy (their next "long term support" release). You thus might
> want to check out the Ubuntu diff (assuming upstream packages are in
> sync) for possible improvements.

I have looked at setools, and if that is an example, there is
 not much help.  They took my package  (just this January), merger 4
 binary library packages into one, converted the build system to use
 CDBS, and added gazillions of files into ./debian.

They seem to have gone out of their way to fork the package.

> http://www.outflux.net/blog/archives/2008/03/16/selinux-in-hardy/

At this point, our packages in Sid are more recent.

> Ideally, you might also convince the Tresys people to work directly on
> Debian so that both Ubuntu and Debian benefit from their work. :-)

Feel free to make the advances. But given the way they have
 forked the packages, I am not currently in the mood.

manoj
-- 
The greatest of faults is to be conscious of none.
Manoj Srivastava <[EMAIL PROTECTED]>   
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C


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

Re: BitTorrent and ISP interference

[Ron Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/20/08 10:46, brian m. carlson wrote:
> [Ignoring the part of M-F-T that indicates Ben Finney, per his request.]
> 
> On Thu, Mar 20, 2008 at 11:31:22AM -0400, Clint Adams wrote:
>> On Thu, Mar 20, 2008 at 08:50:11AM +1100, Ben Finney wrote:
>>> William, please follow the Debian mailing list code of conduct
>>> http://www.debian.org/MailingLists/#codeofconduct>; specifically,
>>> don't send me individual messages that are also sent to the list,
>>> since I didn't ask for them.
>>
>> How many times do people have to cite this stupid thing before someone
>> removes it from the website?
> 
> I think it's a good idea.  I'm not a DD, but I don't appreciate getting
> dupe messages from the list.  procmail is not set up to handle them, and
> I read the vast majority of the lists I post to.  I only wish non-Debian
> lists had the same policy.

Following that rule would be much easier if Tbird and gmail had
Reply To List.

- --
Ron Johnson, Jr.
Jefferson LA  USA

Supporting World Peace Through Nuclear Pacification
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH4orjS9HxQb37XmcRAo1EAKDF+xn8CJulmOkcU4noiv970UvNWwCfewQ+
XPcR/lGR03g+xm9mXuiy9HM=
=YZZw
-END PGP SIGNATURE-


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

Re: BitTorrent and ISP interference

[Milan P. Stanic]

On Thu, Mar 20, 2008 at 11:03:47AM -0500, Ron Johnson wrote:
> On 03/20/08 10:46, brian m. carlson wrote:
> > I think it's a good idea.  I'm not a DD, but I don't appreciate getting
> > dupe messages from the list.  procmail is not set up to handle them, and
> > I read the vast majority of the lists I post to.  I only wish non-Debian
> > lists had the same policy.
> 
> Following that rule would be much easier if Tbird and gmail had
> Reply To List.

Don't know for gmail but there is add-on for thunderbird/icedove at:
http://alumnit.ca/wiki/index.php?page=ReplyToListThunderbirdExtension



signature.asc
Description: Digital signature

disassembling machine code

[PETER EASTHOPE]

Folk,

There was no answer to this question in debian-user.
Is this the appropriate list?

I have these 5 bytes of machine code to disassemble.

b8 12 00 cd 10

I've looked at gdb and objdump.  Appears they 
need a complete object file.  What tool can disassemble 
this string?

Thanks,  ... Peter E.


 http://carnot.yi.org/



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

Re: BitTorrent and ISP interference

[Ron Johnson]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 03/20/08 11:18, Milan P. Stanic wrote:
> On Thu, Mar 20, 2008 at 11:03:47AM -0500, Ron Johnson wrote:
>> On 03/20/08 10:46, brian m. carlson wrote:
>>> I think it's a good idea.  I'm not a DD, but I don't appreciate getting
>>> dupe messages from the list.  procmail is not set up to handle them, and
>>> I read the vast majority of the lists I post to.  I only wish non-Debian
>>> lists had the same policy.
>> Following that rule would be much easier if Tbird and gmail had
>> Reply To List.
> 
> Don't know for gmail but there is add-on for thunderbird/icedove at:
> http://alumnit.ca/wiki/index.php?page=ReplyToListThunderbirdExtension

In Iceweasel, it stopped working at around v2.0.0.6.

- --
Ron Johnson, Jr.
Jefferson LA  USA

Supporting World Peace Through Nuclear Pacification
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH4pa4S9HxQb37XmcRAkZsAKC2720coOnE8ig6uMTedUVLl8l9GwCcCHV6
76ybvlDBpIPlNtCHmAJOMsM=
=00st
-END PGP SIGNATURE-


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

Re: disassembling machine code

[Daniel Jacobowitz]

On Thu, Mar 20, 2008 at 09:25:00AM -0700, PETER EASTHOPE wrote:
> Folk,
> 
> There was no answer to this question in debian-user.
> Is this the appropriate list?
> 
> I have these 5 bytes of machine code to disassemble.
> 
> b8 12 00 cd 10
> 
> I've looked at gdb and objdump.  Appears they 
> need a complete object file.  What tool can disassemble 
> this string?

Try objdump -b binary -D.

-- 
Daniel Jacobowitz
CodeSourcery


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

Re: disassembling machine code

[Ove Kaaven]

PETER EASTHOPE skrev:

I have these 5 bytes of machine code to disassemble.

b8 12 00 cd 10

I've looked at gdb and objdump.  Appears they 
need a complete object file.  What tool can disassemble 
this string?


If all else fails, decode it with your head, maybe? I probably would...

You're giving the bytes, but not saying what kind of CPU it's for. From 
experience, though, this resembles 16-bit 8086 code. Would gdb or 
objdump even understand that?


In Intel syntax, I'd guess it means

mov ax, 012h
int 10

which is how you might set 640x480 16-color VGA mode from MS-DOS code. 
What would it have to do with Debian?




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

Re: I am confused about configuration files

[Artur R. Czechowski]

Russ Allbery <[EMAIL PROTECTED]> wrote:
> "Artur R. Czechowski" <[EMAIL PROTECTED]> writes:
[cut]
> > Is the only way to make sure that conffiles do not clutter filesystem to
> > remove them in maintainer's script on upgrade from previous version?
> I believe that's the case, although I'd like to get some confirmation
> before adding something to Policy 10.7.3 about this.  See Bug#470633.
It doesn't sound good for me. Let's consider fglrx driver. I would like to
stay tuned with fglrx from Debian package. But sometimes I have a problems
running an OpenGL application. In such cases I use an flgrx directly from
ATI to verify if problem exists. If application works I am trying to find
the differences then I submit the bug to fglrx maintainers. The problem is
that init.d script for the daemon required by driver is named in Debian
package differently from ATI package. I believe maintainer of the package
had a reason for doing it[1].

So what should be the proper way to allow switching between ATI and Debian
debs with drivers? Ask the maintainer to rename the init.d script back to
original name? Ask him to delete the ATI init.d script? In this case what to
do when switching from Debian to ATI package? Don't bother anybody about it
and remove the obsoleted files manualy by myself? What would you suggest
in this case?

Best regards
Artur

[1] I'm Cc-ing the maintainer, pleas ask on debian-devel, please.
-- 
Dekolektywizacja stosunków zarządzanie-praca, którą implikuje deregulacja,
oddziaływać bedzie dysfunkcyjnie
  /Raport Międzynarodowego Biura Pracy z 1995 roku/


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

Re: Standard to indicate repacking in version numbers?

[Magnus Holmgren]

On måndagen den 28 januari 2008, Cyril Brulebois wrote:
> On 28/01/2008, Andreas Tille wrote:
> > ... which describes the _content_ of the tarball, but not the _name_
> > (or extension) of the tarball.  So there is no clarification whether
> > to use 'dfsg', 'debian', 'ds' or something else in the tarball name to
> > my knowlwedge.
>
> How are “dfsg”, “debian”, or “ds” extensions? It's in the very middle of
> the tarball name, and the extension would rather be “((orig.)tar.)gz”
> (there's the revision in the way, also).
>
> It'd be clearer to talk about the string to include in version numbers,
> and I agree that having a common pattern in the policy or the devref
> would make sense. There are several combinations of the above, mixed
> together with the use of ‘+’, ‘~’ and ‘.’, and getting a standard for
> that couldn't hurt.

Whatever the suffix, what do you say about always using '-' as the separator? 
Remember that hyphens are allowed in upstream versions. Since hyphens are 
generally used to separate upstream from downstream, it would more clearly 
indicate that the -dfsg* suffix is not really part of upstream's version 
number.

-- 
Magnus Holmgren[EMAIL PROTECTED]
   (No Cc of list mail needed, thanks)

  "Exim is better at being younger, whereas sendmail is better for 
   Scrabble (50 point bonus for clearing your rack)" -- Dave Evans


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

Re: I am confused about configuration files

[Russ Allbery]

"Artur R. Czechowski" <[EMAIL PROTECTED]> writes:

> It doesn't sound good for me. Let's consider fglrx driver. I would like
> to stay tuned with fglrx from Debian package. But sometimes I have a
> problems running an OpenGL application. In such cases I use an flgrx
> directly from ATI to verify if problem exists. If application works I am
> trying to find the differences then I submit the bug to fglrx
> maintainers. The problem is that init.d script for the daemon required
> by driver is named in Debian package differently from ATI package. I
> believe maintainer of the package had a reason for doing it[1].
>
> So what should be the proper way to allow switching between ATI and
> Debian debs with drivers? Ask the maintainer to rename the init.d script
> back to original name? Ask him to delete the ATI init.d script? In this
> case what to do when switching from Debian to ATI package? Don't bother
> anybody about it and remove the obsoleted files manualy by myself? What
> would you suggest in this case?

Give the packages two different names and make them conflict with each
other so that you can purge one and then install the other, maybe?

-- 
Russ Allbery ([EMAIL PROTECTED])   


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

Bug#430896: and author of

[Lukas Audley]

Aquire Precsriptions and Medicaitons right now

www.addictartistry.bifreca.com



on armchairadulate




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

Re: Debian refpolicy and core SELinux package update

[Kees Cook]

Hi,

On Thu, Mar 20, 2008 at 10:48:23AM -0500, Manoj Srivastava wrote:
> On Thu, 20 Mar 2008 09:34:38 +0100, Raphael Hertzog <[EMAIL PROTECTED]> said: 
> > On Wed, 19 Mar 2008, Manoj Srivastava wrote:
> >> I am beginning to come back from a deadline crunch on my day job, and
> >> start paying attention to my Debian packages again; so hopefully the
> >> state of SELinux in Debian will improve -- at least, I'll try to be
> >> more reactive in the future.
> >> 
> >> anyway, kick the tyres, look at the Debian diffs with regards to the
> >> upstream refpolicy.  We should have a dialog about which changes need
> >> to be purged, and which should be fed upstream.
> 
> > Ideally, you might also convince the Tresys people to work directly on
> > Debian so that both Ubuntu and Debian benefit from their work. :-)
> 
> Feel free to make the advances. But given the way they have
>  forked the packages, I am not currently in the mood.

I'd love to see more intercommunication -- Tresys had contacted me about
getting involved in SELinux for Ubuntu, and we were happy to get some
help.  Since getting it to play nice with Upstart and AppArmor needed some
work, no one had yet stepped up to do anything for SELinux in Ubuntu and as
a result SELinux had been virtually unusable there.

I did try to point them your way -- I don't like seeing a delta from
Debian.  I think timing was just off; they wanted newer revisions of
things than what was in unstable when they started their work a few
months back.

> > FYI, it looks like some folks at Tresys did work on SELinux support in
> > Ubuntu hardy (their next "long term support" release). You thus might
> > want to check out the Ubuntu diff (assuming upstream packages are in
> > sync) for possible improvements.
> 
> I have looked at setools, and if that is an example, there is
>  not much help.  They took my package  (just this January), merger 4
>  binary library packages into one, converted the build system to use
>  CDBS, and added gazillions of files into ./debian.
> 
> They seem to have gone out of their way to fork the package.

I don't think this was malicious -- I think they just figured it would
be easier for them to manage future updates in Ubuntu if they used
different packaging.  But I'm just guessing -- I did balk a bit at the
extensive changes, but again, no one else was working on SELinux in
Ubuntu, so we welcomed it.

> > http://www.outflux.net/blog/archives/2008/03/16/selinux-in-hardy/
> 
> At this point, our packages in Sid are more recent.

Again, it's just bad timing -- Ubuntu's feature freeze had been
coming up, so they worked with what they could.  The majority of the
integration work needed for Ubuntu code-wise is upstream now, and the
bulk boot-time packaging bits is limited to the Ubuntu-only "selinux"
package they created.

Anyway, I just wanted to give some background history for all of this.
I don't want to suggest anyone should take anyone else's packaging.  :)

-Kees

-- 
Kees Cook@outflux.net


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

Re: disassembling machine code

[Kees Cook]

On Thu, Mar 20, 2008 at 09:25:00AM -0700, PETER EASTHOPE wrote:
> There was no answer to this question in debian-user.
> Is this the appropriate list?
> 
> I have these 5 bytes of machine code to disassemble.
> 
> b8 12 00 cd 10
> 
> I've looked at gdb and objdump.  Appears they 
> need a complete object file.  What tool can disassemble 
> this string?

I'm biased towards libdisasm's x86dis tool:

$ echo -e '\xb8\x12\x00\xcd\x10' | x86dis -r 0 5 -s att
 B8 12 00   mov $0x0012, %ax
0003 CD 10  int $0x10

-- 
Kees Cook@outflux.net


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

Using apt-file db to find possible conflicts

[Sami Liedes]

[Please Cc: me in replies as I'm not on the list]

Hi,

I don't know if there's any previous work on this, but since I as a
sid user often see conflicts in packages, and I've seen those on
numerous oldstable->stable upgrades, I thought something could be done
about it. Actually, most often oldstable->stable updates seem to me to
have been more like iterative processes, rerun dist-upgrade until no
errors.

So I wrote a script[1] to get a list of packages with identically
named files from the apt-file database and to run `apt-get --dry-run
install' for each pair of these potentially conflicting packages to
see if apt can find a way to install both of them at the same time.

Obviously this doesn't take diversions into account, so any results
should be regarded as merely suspected missing Conflicts:, not
conclusive. However cursory inspection reveals that at least some of
these indeed are known bugs already reported in the BTS, so I assume
this list could be useful. (Is there something else that could make
identically named files in two strongly non-conflicting (i.e. no
conflicting dependencies either) packages legitimate?)

As an example output, here's a list of pairs of co-installable
packages with identically named files from amd64 sid. NOTE: As said
above, not all these are bugs, as these include packages with
diversions (as in, for example, gcc and pentium-builder, I think).


abiword-common abiword-plugins
amanda-server cdrw-taper
apache2-utils mini-httpd
asterisk-sounds-extra asterisk-sounds-main
atftpd tftpd-hpa
atlas3-test libatlas-test
belocs-locales-bin libc6
binutils binutils-multiarch
binutils hardening-wrapper
broffice.org openoffice.org-base
broffice.org openoffice.org-calc
broffice.org openoffice.org-common
broffice.org openoffice.org-draw
broffice.org openoffice.org-impress
broffice.org openoffice.org-l10n-af
broffice.org openoffice.org-l10n-ar
broffice.org openoffice.org-l10n-as-in
broffice.org openoffice.org-l10n-be-by
broffice.org openoffice.org-l10n-bg
broffice.org openoffice.org-l10n-bn
broffice.org openoffice.org-l10n-br
broffice.org openoffice.org-l10n-bs
broffice.org openoffice.org-l10n-ca
broffice.org openoffice.org-l10n-cs
broffice.org openoffice.org-l10n-cy
broffice.org openoffice.org-l10n-da
broffice.org openoffice.org-l10n-de
broffice.org openoffice.org-l10n-dz
broffice.org openoffice.org-l10n-el
broffice.org openoffice.org-l10n-en-gb
broffice.org openoffice.org-l10n-en-za
broffice.org openoffice.org-l10n-eo
broffice.org openoffice.org-l10n-es
broffice.org openoffice.org-l10n-et
broffice.org openoffice.org-l10n-eu
broffice.org openoffice.org-l10n-fa
broffice.org openoffice.org-l10n-fi
broffice.org openoffice.org-l10n-fr
broffice.org openoffice.org-l10n-ga
broffice.org openoffice.org-l10n-gl
broffice.org openoffice.org-l10n-gu-in
broffice.org openoffice.org-l10n-he
broffice.org openoffice.org-l10n-hi-in
broffice.org openoffice.org-l10n-hr
broffice.org openoffice.org-l10n-hu
broffice.org openoffice.org-l10n-it
broffice.org openoffice.org-l10n-ja
broffice.org openoffice.org-l10n-ka
broffice.org openoffice.org-l10n-km
broffice.org openoffice.org-l10n-ko
broffice.org openoffice.org-l10n-ku
broffice.org openoffice.org-l10n-lo
broffice.org openoffice.org-l10n-lt
broffice.org openoffice.org-l10n-lv
broffice.org openoffice.org-l10n-mk
broffice.org openoffice.org-l10n-ml-in
broffice.org openoffice.org-l10n-mr-in
broffice.org openoffice.org-l10n-nb
broffice.org openoffice.org-l10n-ne
broffice.org openoffice.org-l10n-nl
broffice.org openoffice.org-l10n-nn
broffice.org openoffice.org-l10n-nr
broffice.org openoffice.org-l10n-ns
broffice.org openoffice.org-l10n-or-in
broffice.org openoffice.org-l10n-pa-in
broffice.org openoffice.org-l10n-pl
broffice.org openoffice.org-l10n-pt
broffice.org openoffice.org-l10n-pt-br
broffice.org openoffice.org-l10n-ro
broffice.org openoffice.org-l10n-ru
broffice.org openoffice.org-l10n-rw
broffice.org openoffice.org-l10n-sk
broffice.org openoffice.org-l10n-sl
broffice.org openoffice.org-l10n-sr
broffice.org openoffice.org-l10n-ss
broffice.org openoffice.org-l10n-st
broffice.org openoffice.org-l10n-sv
broffice.org openoffice.org-l10n-ta-in
broffice.org openoffice.org-l10n-te-in
broffice.org openoffice.org-l10n-tg
broffice.org openoffice.org-l10n-th
broffice.org openoffice.org-l10n-tn
broffice.org openoffice.org-l10n-tr
broffice.org openoffice.org-l10n-ts
broffice.org openoffice.org-l10n-uk
broffice.org openoffice.org-l10n-uz
broffice.org openoffice.org-l10n-ve
broffice.org openoffice.org-l10n-vi
broffice.org openoffice.org-l10n-xh
broffice.org openoffice.org-l10n-zh-cn
broffice.org openoffice.org-l10n-zh-tw
broffice.org openoffice.org-l10n-zu
broffice.org openoffice.org-math
broffice.org openoffice.org-writer
capi4hylafax hylafax-server
cdecl cutils
cmap-adobe-cns1 xpdf-chinese-traditional
cmap-adobe-gb1 xpdf-chinese-simplified
cmap-adobe-japan1 xpdf-japanese
collectd collectd-apache
collectd collectd-hddt

Re: Using apt-file db to find possible conflicts

[Matthew Rosewarne]

On Thursday 20 March 2008, Sami Liedes wrote:
> I don't know if there's any previous work on this, but since I as a
> sid user often see conflicts in packages, and I've seen those on
> numerous oldstable->stable upgrades, I thought something could be done
> about it. Actually, most often oldstable->stable updates seem to me to
> have been more like iterative processes, rerun dist-upgrade until no
> errors.
>
> So I wrote a script[1] to get a list of packages with identically
> named files from the apt-file database and to run `apt-get --dry-run
> install' for each pair of these potentially conflicting packages to
> see if apt can find a way to install both of them at the same time.

Oddly enough, I just whipped up a similar script [1] for finding conflicts 
between kde3 and kde4 packages.  Instead of finding any conflicts between all 
packages in a Contents-*.gz file, it finds any conflicts between a single 
package and the any of the available apt-file lists.  It's quite stupid as it 
doesn't bother to check for existing Conflicts or Replaces entries, and it 
uses apt-file VERY inefficiently.

Perhaps these two scripts could be combined into something genuinely useful.


[1] http://mrk.homelinux.net/hack/debian/pkg-test/findconflicts.sh


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

Work-needing packages report for Mar 21, 2008

[wnpp]

The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.

Total number of orphaned packages: 368 (new: 9)
Total number of packages offered up for adoption: 95 (new: 7)
Total number of packages requested help for: 40 (new: 1)

Please refer to http://www.debian.org/devel/wnpp/ for more information.



The following packages have been orphaned:

   gnuift (#471251), orphaned 4 days ago
 Description: GNU Image Finding Tool - index and search images by
   content
 Reverse Depends: gnuift gnuift-perl libgnuift0-dev libgnuift0c2a
   libmrml1-dev
 Installations reported by Popcon: 3475

   hk-classes (#471800), orphaned today
 Description: library for database applications
 Reverse Depends: knoda libhk-classes-dev libhk-classes-mdb
   libhk-classes-mysql libhk-classes-odbc libhk-classes-paradox
   libhk-classes-postgres libhk-classes-sqlite libhk-classes-sqlite3
   libhk-classes-xbase (2 more omitted)
 Installations reported by Popcon: 515

   jabber (#471408), orphaned 3 days ago
 Description: An instant messaging server using the Jabber/XMPP
   protocol
 Reverse Depends: jabber-aim jabber-jud jabber-msn jabber-muc
   jabber-yahoo
 Installations reported by Popcon: 618

   knoda (#471806), orphaned today
 Description: graphical database frontend for KDE
 Reverse Depends: knoda libhk-kdeclasses-dev
 Installations reported by Popcon: 510

   licq (#471819), orphaned today
 Description: ICQ client
 Reverse Depends: licq licq-plugin-autoreply licq-plugin-console
   licq-plugin-forwarder licq-plugin-kde licq-plugin-msn
   licq-plugin-osd licq-plugin-qt licq-plugin-rms
 Installations reported by Popcon: 1046

   pgpool (#471824), orphaned today
 Description: connection pool server for PostgreSQL
 Installations reported by Popcon: 34

   pgpool2 (#471826), orphaned today
 Description: connection pool server for PostgreSQL
 Installations reported by Popcon: 12

   postgresql-plruby (#471827), orphaned today
 Description: Ruby procedural language for PostgreSQL
 Installations reported by Popcon: 14

   xbsql (#471820), orphaned today
 Description: SQL wrapper for XBase DBMS library
 Reverse Depends: libhk-classes-xbase libxbsql-bin libxbsql-dev
 Installations reported by Popcon: 203

359 older packages have been omitted from this listing, see
http://www.debian.org/devel/wnpp/orphaned for a complete list.



The following packages have been given up for adoption:

   doclifter (#470885), offered 6 days ago
 Description: Convert troff to DocBook
 Installations reported by Popcon: 61

   egroupware (#471801), offered today
 Description: web-based groupware suite
 Reverse Depends: egroupware egroupware-addressbook
   egroupware-bookmarks egroupware-calendar egroupware-developer-tools
   egroupware-emailadmin egroupware-etemplate egroupware-felamimail
   egroupware-filemanager egroupware-infolog (14 more omitted)
 Installations reported by Popcon: 276

   egroupware-egw-pear (#471821), offered today
 Description: modified PEAR modules for eGroupWare
 Reverse Depends: egroupware-core
 Installations reported by Popcon: 81

   fatsort-gui (#471492), offered 2 days ago
 Description: a really simple gui for fatsort

   gmrun (#471322), offered 3 days ago
 Description: Featureful CLI-like GTK+ application launcher
 Installations reported by Popcon: 255

   php-fpdf (#471822), offered today
 Description: PHP class to generate PDF files
 Reverse Depends: dtc-common egroupware-core ldap-account-manager
 Installations reported by Popcon: 1162

   sl-modem (#471888), offered today (non-free)
 Description: SmartLink software modem driver
 Installations reported by Popcon: 304

88 older packages have been omitted from this listing, see
http://www.debian.org/devel/wnpp/rfa_bypackage for a complete list.



For the following packages help is requested:

[NEW] mantis (#471094), requested 5 days ago
 Description: web-based bug tracking system
 Installations reported by Popcon: 55

   apache2 (#470795), requested 7 days ago
 Description: Co-maintainer wanted
 Reverse Depends: adzapper ampache apache2 apache2-dbg
   apache2-mpm-event apache2-mpm-itk apache2-mpm-perchild
   apache2-mpm-prefork apache2-mpm-worker apache2-prefork-dev (145 more
   omitted)
 Installations reported by Popcon: 37124

   apt-build (#365427), requested 691 days ago
 Description: Need new developer(s)
 Installations reported by Popcon: 965

   ara (#450876), requested 130 days ago
 Description: utility for searching